Support 1a

[Support 1a]

Sorry for the delay.

I have have been able to reproduce the problem with the dissapearing properties in the Object Inspector. We are currently working on a resolution.

You should be able to activate the Object by calling the ‘DoVerb()’ method of the TOleContainer. However, this method is not working, and I think it may be related to the first issue. I’ll let you know when I learn more.

Thank you for your patience.

Regards,

Advansys Support

[Support 1a]

I don’t think you are missing any registry entries. To assist further, could you please post/email a copy of the configuration information from a machine where the applet doesn’t appear to work. You can access the configuration information from the main GroupWise menu: select Help | About Formativ. When the About box appears, select the configuration tab. Press the ‘Copy to clipboard’ button, then paste the contents of the clipboard into your reply posting.

Could you also send a copy of the applet you are using. These two items should make it easier to troubleshoot the problem.

There isn’t any inherent way to change the target base folder from the Windows system-determined Program Files location. This location is the only location we can install to and still comply with Windows standards, so the ability to change the base location wasn’t exposed. The location of Formativ won’t have any affect on the problem you are having removing the menu entries.

Regards,

Advansys Support

[Support 1a]

Thanks for your post below.

We are not aware of any inherent problems witht the upgrade from Admin to Studio. Could you please post a copy of your configuration information (or email it to support@advansyscorp.com).

You can access the configuration information from the GroupWise main menu. Select Help | About Formativ. When the About box appears, select the configuration tab. Press the ‘Copy to clipboard’ button. Paste the contents of the clipboard into the thread reply (or message to support as detailed above).

Regards,

Advansys Support

[Support 1a]

What string value does:

Groupwise.Envversionname()

return on the workstation(s) where this doesn’t work? (I see from your example that you check for version 6.5.2 twice – that might be a typo).

If the applet is running, then the problem most likely lies in the line where you check the version of the client. I would suggest you insert a MsgBox to see what value the version check is returning on the offending clients.

Please let me know how you proceed.

Regards,

Advansys Support

[Support 1a]

Could you please provide more information about the problem you are experiencing? Some sample code would assist. You can email any sample code to support@advansyscorp.com.

Thank you.

Advansys Support

[Support 1a]

I am not aware of any standard means by which you could query this information. I suspect you would need to query the native application before it was shut down to determine this kind of information. The actual approach would vary based on the application in question.

Regards,

Advansys Support

[Support 1a]

Formativ doesn’t provide any native twain support. You would need to use a third party twain component, preferably one that could be instantiated via COM automation.

http://www.twain.org is probably a good place to start.

Regards,

Advansys Support

[Support 1a]

Thank you. We’ll take a look at the code.

Regards,

Advansys Suport

[Support 1a]

We tried a test scenario, and found that we couldn’t tab back to the draft message, so I guess your approach must be different. We really need to see your applet in order to assist. If you are willing to share this with us on a confidential basis, please email it to support@advansyscorp.com and we’ll take a look.

Regards,

Advansys Support

[Support 1a]

We (Advansys) are in the final stages of implementing a solution that does exactly this. I couldn’t locate an email address for you in the forum member database, so if you would like to send an email to support@advansyscorp.com, we could get in contact and see what we can do.

Regards,

Advansys Support

[Support 1a]

OK. Thanks for the update. Let me know if you would like to take this further. If it’s something I can duplicate (I might need your exact file and applet to do this) we would be happy to pass it on to Novell.

Advansys Support

[Support 1a]

Thank you for your post above. We’ve not seen this error previously. The ‘TPH’ mentioned could be either a Formativ component, or a third party component.

Could you try uninstalling Formativ Runtime, then re-installing. If the problem persists, please send the Formativ Configuration information to support@advansyscorp.com. You can access the configuration information from the main GroupWise menu: Help | About Formativ. When the About box appear, select the configuration tab. Press the ‘Copy to Clipboard’ button, then paste the contents of the clipboard into a message body.

Regards,

Advansys Support

[Support 1a]

Dear Tarquin,

The additional space before each line-break could be a result of the encoding of your line breaks in the file. From memory GroupWise prefers CR/LF pairs (i.e. #13 #10). Some files, (notably those from Unix) use other conventions that can throw GroupWise out.

I do recall problems with message body text handling on some older versions of GroupWise (5.5?), but thought most of them had been fixed by Novell. Again, you may wish to check the character encoding in your file.

Regards,

Advansys Support

[Support 1a]

The mininum version of GroupWise that a Formativ Portal will work with is 5.5.7.1 Enhancement Pack client with the FTF update. See Novell TID 2963458 to download the GroupWise 5.5.7.2 Beta FTF file (f32eppp1.exe). http://support.novell.com/cgi-bin/search/searchtid.cgi?/2963458.htm.

Technically, we are unable to implement our portal technology with clients earlier than this.

Regards,

Advansys Support

[Support 1a]

Unfortunately I don’t think this settings is exposed, either to read or write.

Regards,

Advansys Support

[Author]

Replies