Support 1a

[Support 1a]

Thank you for your posting. I’ll ask an engineer to take a look at your code, though from a glance it looks OK.

All the commands you use in this code are direct wrappers over the top the native GroupWise tokens. This infers a native GroupWise token is failing, as opposed to anything in the language.

I’ll defer a full commentary until an Engineer takes a look, but I would probably move the Utilities.DoEvents() down to after the ‘Call Groupwise.focusSet(fcsMessage, “”)’ line, as this seems to be the area where the process fails. It could be that the Windows message queue is not being flushed, and thus the focus is not being reset, or the PosTextTop() command is not working.

In any case, we’ll respond any additional suggestions here.

Regards,

Advansys Support

[Support 1a]

Novell have confirmed this as a bug, and have assigned it defect #404244. Novell have indicated they hope it will be addressed more quickly given the token used to work.

I’ll post an update to this thread when I hear something.

Regards,

Advansys Support

[Support 1a]

Tim,

Thank you for your question above. We tested the solution with an English 6.5.3 (18/11/2004) client this morning and it included all attachments.

Do you see this problem with all messages you try to print? Are you trying to print messages from a shared folder, or somewhere other than your mailbox?

If it happens with all messages, perhaps you could send a message to yourself containing attachments and try to print it. If it fails, please forward the same message (as an attachment) to support@advansyscorp.com and we’ll see if we can duplicate the problem with the same message.

Regards,

Advansys Support

[Support 1a]

Dear Thomas,

Thank you for your posting. I can confirm that I can also duplicate this failure with the 6.5.4 beta GroupWise client. It would appear Novell have broken the underlying ItemAttachmentGetCurrentIndex() token used by this language extension.

I have written to Novell this morning to ascertain the status of this command. I’ll report my finding via this thread.

At this stage I cannot offer any workarounds that would let you identify the selected attachment.

Regards,

Advansys Support

[Support 1a]

Thanks for the update. Glad to hear things are now working as they should.

Regards,

Advansys Support

[Support 1a]

Given you are unable to load other C3PO’s, I suspect you have a faulty GroupWise client installation.

I have seen one other instance where a mismatch of GroupWise client files would stop any C3PO from loading. This was bought about by a fault Zen-based client installation. The problem was solved by uninstalling GroupWise, then re-installing from a CD.

I would suggest you uninstall your GroupWise client, check all files are gone, then re-install from a CD or software distribution directory known to be sound.

I hope this helps,

Advansys Support

[Support 1a]

Dear Greg,

Yes, it would be possible to create a help desk/ticket system using Formativ and GroupWise. Unfortunately we (Advansys) don’t have any existing commercial solutions available that you could buy off the shelf.

We do have a couple of examples of support request applets written in Formativ I could make available to you. Please write to support@advansyscorp.com if interested.

I hope this helps.

Advansys Support

[Support 1a]

Formativ doesn’t let you create new toolbars. It does, however, let you add toolbar buttons to existing toolbars in the GroupWise client.

You would need to write an applet that inserted the text into the appropriate control when executed. Have a look at the GroupWise.ItemSetText() and GroupWise.TypeText() methods in the Formativ Language Guide.

The distribution methods are detailed in the Formativ Studio User Guide. Your options are basically a) use eDirectory/NDS, and b) copy the applet file to a known location.

Each workstation would require a copy of Formativ Runtime to be installed.

I would suggest you download a 30 day trial copy of Formativ Studio and review the Language and Developers Guide. They should contain enough information to get you started.

I hope this helps.

Advansys Support

[Support 1a]

The solution probably depends on your Citrix configuration. The ‘every time I start’ setting is stored under the following key:

HKEY_CURRENT_USERSoftwareAdvansys Corporationformativ1.0Settings

Value Name:
Redirect Associations

Value:
0 = False

You would need to ensure all users have this value set to 0.

I hope this helps.

Adavansys Support

[Support 1a]

We don’t run anything on machine startup, so I can’t think of anything Formativ-related that would be causing this. Are you running the ‘restore association’ process logged in as an Administrator?

Advansys Support

[Support 1a]

Thanks for the update.

Advansys Support

[Support 1a]

No problems.

Advansys Support

[Support 1a]

Dear Matthew,

Thank you for your questions above.

quote:

---

1. Users that are CC’d or BCC’d on a message CANNOT use the Reply function on the message.

---

I don’t think this would be possible. GroupWise doesn’t provide any inherent way to stop people from being able to reply to a message. It also doesn’t provide a means by which we can ascertain if a recipient is receiving a message because they were a CC or BCC recipient.

quote:

---

2. We can limit the number of addressees that are chosen in the To, CC & BCC fields.

---

This could probably be done by integrating an applet to run on the send event. You could query the CC and BCC fields on send to see how many recipients had been chosen. If the number exceeded some limit the send could be cancelled. See the GroupWise.ItemGetText() commands to get started.

I hope this helps.

Advansys Support

[Support 1a]

Dear Mike,

Thank you for your question above. The answer depends upon the implementation of the ActiveX control.

Neither Formativ 1.6 or Formativ 2.0 will let you use custom visual ActiveX controls in a ‘drag and drop’ fashion. I.e. you can’t add third party controls to the pallete, then drop them onto a Formativ form.

Both versions of Formativ _will_ let you instantiate an instance of an ActiveX control using CreateObject(). You pass the ProgID of the ActiveX control to CreateObject. You can then call the methods of the ActiveX using the object returned from the call to CreateObject.

We use this technique to create and use instances of the Novell eDirectory NDS ActiveX controls in both Formativ 1.6 and 2.0.

You would have to ask the ActiveX vendor for details of the ProgID. Alternatively, if you know what you are looking for, you can usually locate in the ProgID in the Windows Registry.

If this approach doesn’t work (and it won’t work with all ActiveX controls – some require you to drop them into a form in order to work), the only other option would be to use something like Visual Basic, Delphi or C++ to create an Automation Server/COM object, and drop your Active X control onto a form hosted inside the server. You would then create an instance of the server from within Formativ (again using CreateObject) and call methods on the object via methods you expose in your Automation server. Of course, you would also need to distribute and register your automation server along with the applet.

I hope this helps. Please let me know if any of this description isn’t clear.

Regards,

Advansys Support

[Support 1a]

It sounds like a message that was to be attached to a reminder message has been deleted from your mailbox.

I’ll email you an updated version that should solve this problem.

Advansys Support

[Author]

Replies