Support 1a

[Support 1a]

If you mean draft messages that have been saved into the Work in Progress folder, you would have to call the .Save method of the attachment object, then open the file to determine its size (slow and clunky).

If you are using GroupWise 6.5 SP2 or greater, you can use the AttachmentSize property of the Attachment object.

For more details see:

http://developer.novell.com/ndk/doc/gwobjapi/gwobjenu/data/hjwaqkjd.html

Hope this helps,

Advansys Support

[Support 1a]

Thanks for the suggestion.

Advansys Support

[Support 1a]

The Client argument is documented in the Developers Guide. It is a native GroupWise Client object. Here’s some information from the Developers Guide, which also contains a link to online documentation:

Client: This argument represents the state of the GroupWise client at the time your applet was executed. It is the same as the GroupWise C3PO ClientState Object. Your applet should not assume a specific Client object is in a particular state. Rather, the ClientName, MajorVersion, and MinorVersion properties should be checked to identify the appropriate state of the object. Full documentation of the Client argument can be found at: http://developer.novell.com/ndk/doc/gwc3po/gwc3penu/data/hye3ji8g.html

All other objects are documented in the Language Guide. In terms of the message store access object you mention, search for ‘composingitem’ and ‘account’ in the index.

I hope this helps.

Advansys Support

[Support 1a]

Dear Jeroen,

Thank you for your question above. Unfortunately Formativ 2.0 does not provide step debugging facilities you describe. Including step debugging facilities for Formativ (which runs inside the GroupWise process) is a non-trival task. Nonethess, we know this is an important feature and has been slated for a future release.

In the meantime, you can use other techniques to approximate step debugging. Perhaps the most useful is to include trace output commands in your Applet, then use any debug output viewer capable of intercepting calls to the Win32 OutputDebugString() function.

Through the use of strategically-placed trace commands, you can get a real-time picture of the execution of your Applet. Trace commands are created through the use of the Utilities.Trace() method. Utilities.Trace() takes a single string argument. The string value you supply is output to any attached debugger in real time as the Applet executes.

Utilities.Trace() ultimately uses the Win32 function OutputDebugString() to output the string value. This function sends a string to the debugger for display. If GroupWise has no debugger attached, the system debugger displays the string. If GroupWise has no debugger and the system debugger is not active, OutputDebugString() does nothing. If you use the SysInternals DebugView utility, you only need to run DebugView prior to starting GroupWise – you do not need to attach it to the GroupWise process.

We use and recommend the free DebugView utility from SysInternals: http://www.sysinternals.com/ntw2k/freeware/debugview.shtml

I hope this helps.

Advansys Support

[Support 1a]

Yes, this is possible using Novell NDS ActiveX controls. You can download these from Novell.

Here is a very simple example:

'-------------------------------------------------------------------------------
' Read Novell eDirectory Example
' Designed by: Formativ Business Solution Team
' Copyright (c) 2002 Advansys Corporation (www.advansyscorp.com)
' Version 1.0
'
' Description:
' This is an example of reading user phone numbers out of eDirectory using
' Formativ.  Before running the example, you must:
' 
' 1) Download and install the Novell Controls for ActiveX from
'    www.developer.novell.com/ndk/ocx.htm
' 
' 2) Edit line "oSession.Fullname =" below, inserting the full path of the tree
'    and context you wish to browse.
'
' 3) Be authenticated to eDirectory
' 
' This is a very simple example with no error checking, etc.  It can be easily
' extended to use any of the features found in the Novell ActiveX controls, 
' including updating field values, etc.
'
' INTEGRATIONS: There are no integrations defined apart from appearing on the
'               Formativ Applet Run Menu.
'-------------------------------------------------------------------------------

Sub Main(Client, GWEvent)

  Dim oSession
  Dim ServerNames
  Dim Entries
  Dim Entry
  
  ' Create an instance of the NWDir COM object
  Set oSession = CreateObject("NWDirLib.NWDirCtrl.1")

  ' Specify the name of the tree "<tree name>" and context "<ou>" you wish to browse
  ' for example, oSession.FullName = "NDS:\<tree name><ou>...<ou> etc."
  oSession.FullName = "NDS:\<tree name><ou>"
    
  ' Display each user and their phone number
  Set Entries = oSession.Entries
  for each Entry in Entries
    if Entry.Layout.Name = "User" then
      PhoneField = Entry.GetFieldValue("Telephone Number", "", True)
      Call MsgBox("User: "& Entry.ShortName & "  Phone Number: " & PhoneField(0),,"Formativ")
    end if  
  next
  
  Set oSession = nothing

End Sub

I hope this helps.

Advansys Support

[Support 1a]

No problems. Your post has been answered in the other forum.

Advansys Support

[Support 1a]

You should also ensure an attachment is a file before you attempt to determine its file size using this technique.

Please note this method will only work with draft messages that have not yet been saved to Work in Progress.

Advansys Support

[Support 1a]

I would suggest you uninstall both the Message Saver Pack and Formativ Runtime first.

Check to see that the following directory is empty: If not, delete (or rename) it:

‘C:DocumentiAdvansysFormativApplets’

I noticed the following paths in your config data:

AdvansysFormativ1.0Applets – (System)
AdvansysFormativ1.0Data – (System)
C:ProgrammiAdvansysFormativHelp – (System)
AdvansysFormativ1.0System – (System)

The only one with a drive letter designation is ‘C:ProgrammiAdvansysFormativHelp’. I don’t know why the others simply start with ‘Advansys’, but I suspect this may be a problem. It looks like the standard common application data folder location could not be determined during installation. These locations are determined by calling a standard function that is part of Windows. I have not heard of any problems with the locations of these foldering being determine on Windows 98SE before. I suspect you may have a problem with your installation of Windows 98SE.

The only suggestion I can make at this time might be to install the latest version of Internet Explorer, and all available service packs, then try installing Formativ Runtime again. This process may install/update the system components required to allow the determination of these locations to be made. You would know if this worked by checking your Formativ configuration again – all the paths under ‘Location of Files’ should start with a drive letter.

I hope this helps.

Advanys Support

[Support 1a]

The only was you could do something like this would be to use the AddressBook component (ActiveX) exposed in Formativ 2.0. This lets you select objects from the Address Book UI, and access some of the key data related to the selected item(s).

I am not aware of any other API you could use to display the Address Book UI and access data.

I hope this helps.

Advansys Support

[Support 1a]

Dear David,

I cannot explain the behaviour you describe, but I suspect it may be related to roaming profiles. When Formativ is installed it writes a value to the following key in the registry:

HKEY_CURRENT_USERSoftwareNovellGroupWiseClientThird Party

The value is the path to the tokenblocker.dll file referenced in the error. When GroupWise loads, it attempts to load any files referenced under this key.

Are you using roaming profiles? If so, it could be that the user’s ‘HKEY_CURRENT_USERSoftwareNovellGroupWiseClientThird Party’ key is being replicated to every machine they access. This would tell GroupWise that it should attempt to load the DLL, when in fact it can’t because the file doesn’t exist on the machine. Unfortunately, we can’t suppress this warning message as is eminates from GroupWise.

Should roaming be the problem, the only solution I can think of would be to install Runtime on the offending machine (it wouldn’t need to be registered), or to configure this registry key as an exception to roaming (if possible).

I hope this helps.

Advansys Support

[Support 1a]

Thank you for your question. While we may seek 6.5 Yes Testing certification in future, we do not have plans at this time. We do intend to support 8.8 in the future. As Formativ’s eDirectory support is based on basic directory standards and techniques, we do not expect any issues with upward compatibility.

I hope this helps.

Advansys Support

[Support 1a]

I can reproduce this by manually retrieving a HTML file containing a table into a message. It’s been difficult so far to try to determine which HTML elements (and/or the orientation of the elements) cause the problem.

I’ve contacted Novell to see if they are aware of the issue, and if they have any additional information.

I’ll let you know what I learn in this thread.

Regards,

Advansys Support

[Support 1a]

We will post a response here as soon as possible.

Regards,

Advansys Support

[Support 1a]

We are attempting to duplicate this internally. As QuickCorrect and the HTML message editor are both GroupWise features, this behavour doesn’t represent a bug in Formativ. The only resolution we may be able to provide is a possible modification to the HTML structure

I’ll let you know what we discover via this thread.

Advansys Support

[Support 1a]

For messages the user creates, I would suggest the OnSend event. From that point you should be able to access the CommandMessage’s categories collection, ennumerate it to see if the user has set a category, and update the category if required.

You could also try the OnCompose event, but that wouldn’t give the user the opportunity to set a category themselves.

I hope this helps,

Advansys Support

[Author]

Replies