Support 1

[Support 1]

Roland,

It may be worthwhile testing to ensure that, in the event of a crash, your log entries have been saved to the log file. This is because the text may not be flushed from memory to disk until the line

  tempfile.Close

executes, or the memory buffer is full.

A simple way to test is to write an applet which fails to call tempfile.Close.

It may be worth also looking at function Utilities.Trace which is documented in the Formativ Language Guide. This is particularly useful for debugging an applet with the help of an external debug event viewer.

Regards,
Advansys Support

[Support 1]

Thank you for your enquiry.

The README.TXT file installed with Formativ 2.0 includes the following (in section 4. Forms Designer):

The components on the Standard, Additional, Win32, System and Dialogs tabs of the component palette are documented in the Borland Delphi VCL help file. This can be downloaded from: ftp://ftpc.borland.com/pub/delphi/techpubs/delphi6/d62pro.zip

The components of the Enhanced tab of the component palette are documented in the Raize Components Trial Help files. This can be downloaded from:
http://www.raize.com/DevTools/RzComps/DemoTrial/RC3Trial.zip

The components on the Netware, LDAP and NDAP tabs of the component palette are Novell’s ‘ActiveX Controls for Novell Services’. Documentation for these components can be found at: http://developer.novell.com/ndk/activex-index.htm.

The components on the GroupWise tabs of the component palette are Novell’s ‘GroupWise Controls for ActiveX’. Documentation for these controls can be found at: http://developer.novell.com/ndk/gwactive.htm.

Regards,
Advansys Support

[Support 1]

Thank you for your enquiry.

I believe you are referring to the installer for Message Saver Pack 1.3.

Actually, it’s not the installer but either Message Saver or Message Viewer which creates the CONFIG.INI (and its containing folder, if necessary).

Could you post more information about the problem, please? That is, what do you mean by “it complains?”

I wonder if the failure that you describe is to do with a user rights issue. When you install, are you logged in as an administrator or normal user? Do you install for the logged-in user or for all users?

Regards,
Advansys
Support

[This message was edited by Support 3 on November 02, 2005 at 10:26 PM.]

[Support 1]

My apologies for misinforming you about HtmlEncode. In fact this function is for encoding characters deemed ‘special’ in HTML, eg. “&” is encoded as “&”.

If you need a general-purpose routine for encoding a URL, you will need to write one (unless you can track down some source code via the Web, say). Google turns up this reference on which characters must be encoded.

I hope this is helpful.

Regards,
Advansys Support

[Support 1]

In your sample, sFileName should be encoded so it is a valid component of a URL (“file://…” in this case). You can do this with Formativ:

  dim iFileName
  dim oHtmlDom

  set oHtmlDom = Utilities.HTMLDom
  iFilename = oHtmlDom.HTMLEncode("C:Program FilesGroupWiseGroupWise.exe")
  ...

You may need to use other methods of HTMLDom to do all that’s needed, eg. DosPathToUnixPath.

I hope this helps you.

Regards,
Advansys Support

[Support 1]

David,

Thank you for your post.

The magnitude of the component documentation for Formativ 2.0 dictated we had to release the product prior to amalgamating component documentation. Prior to official documentation becoming available, component information can be accessed from the following sources:

The components on the Standard, Additional, Win32, System and Dialogs tabs of the component palette are documented in the Borland Delphi VCL help file. This can be downloaded from:
ftp://ftpc.borland.com/pub/delphi/techpubs/delphi6/d62pro.zip

The components on the Enhanced tab of the component palette are documented in the Raize Components Trial Help files. This can be downloaded from:
http://www.raize.com/DevTools/RzComps/DemoTrial/RC3Trial.zip

The components on the Netware, LDAP and NDAP tabs of the component palette are Novell’s ‘ActiveX Controls for Novell Services’. Documentation for these components can be found at: http://developer.novell.com/ndk/activex-index.htm

The components on the GroupWise tabs of the component palette are Novell’s ‘GroupWise Controls for ActiveX’. Documentation for these controls can be found at: http://developer.novell.com/ndk/gwactive.htm

Regards,
Advansys Support

[This message was edited by Support 1 on August 04, 2005 at 05:44 PM.]

[Support 1]

Thank you for your enquiry.

For reference documentation on the components on the Component Palette of the Visual Forms Designer, please take a look at this Support Forum post.

The Formativ Studio/Creator Developers Guide contains an introduction and usage guidelines on the Visual Forms Designer in the section Creating User Interfaces.

However, I think we all find it helps to learn from examples. Please feel free to ask if you have a question on how to do something specific with Visual Forms.

Regards,
Advansys Support

[Support 1]

Thank you for your enquiry.

The SmartFields Assistant, which is bundled with Multiple Signatures, can be used to:

• determine the SmartFields which are available in your GroupWise environment;
• distinguish between your environment’s resources (Account, System Address Book, eDirectory/NDS).

I gather that it’s an HTML signature in which the SmartFields are appearing double-spaced. If so, it may be that there are <P> (paragraph) markers between the lines, or at the end of the signature. You could try using the signature editor to:

• delete white-space that follows the signature;
• ensure that there is only a <BR> (break) marker between each line – first delete the line-break then press SHIFT+ENTER to insert a break marker (which is not visible – you should see a line-break inserted).

Alternatively, you could use a dedicated HTML or text editor to edit the signature to explicitly remove unwanted paragraph markers.

I hope this helps, and look forward to hearing about your progress.

Regards,
Advansys Support

[This message was edited by Support 3 on July 06, 2005 at 05:31 PM.]

[Support 1]

Thank you for your enquiry.

Could you tell me what version of Multiple Signatures you are using? You can see the version on the About box: click About… under the Options menu on the main dialog of this solution.

In addition, are you running GroupWise in Online or Remote/Caching mode? And, which version of GroupWise are you using?

I look forward to your response.

Regards,
Advansys Support

[Support 1]

FYI: This issue was resolved by upgrading the Novell eDirectory/NDS ActiveX controls from version 2.0 to 2.2.

Advansys Support

[Support 1]

Thank you for your enquiry.

While it is not possible to change the Subject field (eg. on a GroupWise Mail composing view), a Formativ solution could do what you describe.

For example, a custom Formativ solution could be developed, which:

• Allows for the definition of a list of different ‘predefined’ subjects (by an Administrator or the end-user).
• Is used to create the required GroupWise message (Mail, Appointment, Task, etc.) and insert the desired predefined subject into the composing message Subject field.

I am not aware of an existing solution like this. Would you be interested in doing your own custom development? Advansys may be available to develop this solution if you prefer.

I hope this information is helpful.

Advansys Support

[Support 1]

If you wish to define a Boolean-valued custom field, then you could replace the constant fgwString by fgwNumeric in the above code examples. However, since every variable in VBScript is a Variant, you could assign a Boolean value to a string-typed field, and the value will be stored as a valid string representation.

In some cases you may need to use explicit type coercion when writing and reading a Boolean value (but this is not usually necessary), as in the following:

  oCheckBox.Checked = CBool(oField.Value)

You can review the range of available constants in the Formativ Language Guide. To see these, go to the Contents tab and select Reference | Constants | eFieldType.

I hope this information helps you.

Regards,
Advansys Support

[Support 1]

Dear Brian,

Thank you for the version information. We have confirmed that there is a defect in (at least) GroupWise 6.0.4 which would cause this behaviour.

I will be contacting you by email to advise you of a workaround to this issue.

Regards,
Advansys Support

[Support 1]

Thank you for your enquiry above.

Is the problem you mention to do with the Portals solution? In the following I will assume this is true.

Which version of GroupWise are you using? It’s possible that a known GroupWise defect is causing your Portals configuration to be uneditable. We may need to update Portals with a workaround to this issue.

Regards,
Advansys Support

[Support 1]

Thanks for letting us know about the outcome of your rollout. It’s good to hear you were successful!

Advansys Support

[Author]

Replies