Support 3

[Support 3]

Good luck. Let us know, if you have any questions.

Regards,
Advansys Support

[Support 3]

Hi Christian,

Thanks for your post. As we stated “if provided, the open source applet version will be installed”.

However, you can send a message to “support@advansyscorp.com” and request the source of the solution. We usually request to provide us with any changes that you will make to the source. If it is something we feel may be useful to other GroupWise users, we could consider publishing an update to the GroupWise Cool Solutions community.

Regards,
Advansys Support

[Support 3]

If the message not saved (i.e. Message ID “X00”) then you can only access limited properties of the message. Formativ wrap the Novell Token API to easily access these properties.

In order to access the message property which is not available in Token API (i.e. formatted body text, etc), you will need to use the Object API. You can use the technique in other thread to save the message which will lets you to access the Object API.

Regards,
Advansys Support

[Support 3]

This issue is similar to your previous post about accessing formatted text from the subject.

You will need to use the Object API to access the formatted body text.

  
msgbox oMsg.BodyText.RTF

Regards,
Advansys Support

[Support 3]

Unfortunately Token API only return the plain text format of the subject. ItemGetText() token may be working as designed to return the plain text format of the subject, unless Novell decide to update or add another Token API to return RTF format.

In order to extract the RTF property of the subject, you will need to use the Object API. If you are working with a draft message (which is not yet saved to the message store) then you will need to save the draft message.

The sample code below save the message to Work-Folder (if the message ID “X00”) then use the Object API to access the RTF property.

  
Sub Main(Client, GWEvent)

  dim iWIPFolderPath
  dim oMsg
  dim iMsgID
  dim iWIPPath
  dim iBreakCount


  ' Get the message ID
  iMsgID = GroupWise.ItemMessageIDFromView

  ' If the draft message then save to WIP otherwise access the message
  if (iMsgID = "X00") then

    ' Save the message to WIP
    call GetWIPFolderPath(groupwise.account.workfolder, iWIPPath)
    msgbox "Work In Progress folder path: " & iWIPPath
    Call Groupwise.throwtoken("ItemSaveMessageDraft(""" & iWIPPath & """)", iReturnVal)

    iBreakCount = 0
    while (iMsgID = "Token failed execution!") or (iMsgID = "X00")
       Application.ProcessMessages
       utilities.Timer(1)
       Application.ProcessMessages
       iMsgID = GroupWise.ItemMessageIDFromView
       iBreakCount = iBreakCount + 1
       Utilities.Trace iBreakCount & ": " & iMsgID
       if (iBreakCount > 10) then
         exit sub
       end if
    wend

    set oMsg = GroupWise.Account.GetMessage(iMsgID)

  else
    set oMsg =  Client.clientstate.commandmessage
  end if

  msgbox "Subject-Plaintext: " & oMsg.subject.plaintext & vbcrlf &_
  "Subject-RTF: " & oMsg.subject.RTF

End Sub

Hope this helps.

Regards,
Advansys Support

[Support 3]

Thanks for the post.

We can re-produce the behaviour with GroupWise Client 7.0.3 (build 8/03/2008). It appear a bug in the GroupWise ItemGetText() token which return the space between the style (Bold and Italic).

We will report this issue to Novell and post any update in this thread.

Regards,
Advansys Support

[Support 3]

Great news. Thanks for letting us know.

Regards,
Advanys Support

[This message was edited by Support 3 on August 20, 2008 at 02:46 PM.]

[Support 3]

We haven’t had any report about this issue. We are running GroupWise client 7.0.3 and able to view the SmartFields under AddressBook and eDirectory. May be you need to upgrade the GroupWise client to latest point release.

Hope this helps. If you have any further questions, please do not hesitate to contact us.

Regards,
Advansys Support

[Support 3]

Thanks for your feedback.

Regards,
Advansys support

[Support 3]

Thanks for your post and sorry to hear about the issue.

We have developed plenty of solutions, with and without Raize controls, which work very well and never raised AV errors. Please see below the known issues which are documented in ReadMe.txt (C:Program FilesAdvansysFormativ).

quote:

---

6. Known problems, issues and omissions

– A small number of component property editors in the Forms Designer are not enabled in this release.
– The Code Explorer does not dynamically update as source code is edited. You need to reselect an applet to see any changes applied in the Code Explorer.
– In some circumstances portal window navigation buttons move to the left of the portal toolbar.
– The editor Replace function does not always make selected text visible.
– Checking the state of the Focused property in some visual controls causes the current subroutine to exit without raising an exception. A workaround is to check if the control in question is the active control, i.e. ‘if .ActiveControl is btnButton then’.
– The Object Inspect scrollbar does not always appear when running on Windows XP. Dragging out the width or the height of the Object Inspector forces the scrollbar to appear.
– The editor does not remember the ‘find text at cursor’ settings.
– Double-clicking on an event in the Object Inspector generates code for a new handler, but a parameter that’s passed by reference (as documented) is not preceded by the ByRef keyword. Add the ByRef keyword manually.
– Not closing certain item editors in the Form Designer prior to saving the form may cause an access violation. You should manually close any popup form editors prior to saving a form.

---

Please see below some suggestions from the engineers:

– The issue could be specific to a machine. Can you re-produce the behaviour in another machine?
– Could be an issue to do with XP (or Vista) themes or ImageList. Please see the forum post about using an ImageList with GroupWise 7 and Windows XP.
– It could be relate to the structure of Form. Perhaps it has many components relationships hardwired together that it’s gone beyond some (Dream or Formativ) limit that we don’t know about.
– Please make sure to close any pop-up item editors windows prior to save the Form.

The difficulty is usually in figuring out which component(s) is responsible for the problem. Using the process of elimination, however, you can usually narrow the problem down rather quickly by making small logical changes and observing the impact on the problem. The key is to make only one change at a time and then see if the problem goes away.

Hope this helps.

Regards,
Advansys Support

[Support 3]

We have sent the updated version (2.0.30) to you. Please let us know if the updated version solved the behaviour.

Regards,
Advansys Support

[Support 3]

Are you getting the error (“Cannot create NDAP ActiveX controls”)?

If so, and if you have already installed these controls, there is another step required to make them work. Please find the file Regocx.bat in the ActiveX controls installation folder, usually C:Novellndkactivex_ndap, and double-click the file to run it. (This is explained in the Help file in the installation folder: SDK_README.html.)

Regards,
Advansys Support

[Support 3]

Sorry, we have received similar report in another post, we have sent an updated version to the user but haven’t receive any update whether it has fixed the issue.

We will send you the updated version via email shortly.

Regards,
Advansys Support

[Support 3]

It could be an environmental issue, which version of the GroupWise client she is running (see Help – About GroupWise)? Are the both machine running the same GroupWise version? We recommend to upgrade the GroupWise client to the latest point release.

Could you please let us know the exact error message and the line number.

Regards,
Advansys Support

[Support 3]

Formativ framework is installed for all users and its not possible to install different type (i.e. Runtime, Studio, Creator) on same machine.

Regards,
Advansys Support

[Author]

Replies