Support 1

[Support 1]

Thank you for your enquiry.

Can you provide more information about how the code does not work? For example, does it fail on the line:

  set AdressBuch = AdressBuecher.Item("TTT")

or on the line:

  AdressBuch.Delete()

Is an error message displayed? What is your installed version of GroupWise?

You could try something like the following to confirm the name of the address book you wish to delete:

'-------------------------------------------------------------------------------
Sub Main(Client, GWEvent)

  dim iText
  dim oBooks
  dim oBook

  iText = ""

  set oBooks = GroupWise.AddressBooks
  for each oBook in oBooks
    iText = iText & oBook.Name & vbNewLine
  next
  set oBooks = nothing

  MsgBox iText, , "Address Book Names"

End Sub
'-------------------------------------------------------------------------------

I hope this helps.

Regards,
Advansys Support

[This message was edited by Support 1 on June 27, 2006 at 10:04 PM.]

[Support 1]

L.P.,

What is the error reported when you try the following?

  set DocBid.Author = DocBid.Creator

I would not expect this to work without using the set operator. set is not a Formativ command, rather it is a VBScript operator to be used when assigning an object reference to a variable. In this case, you are assigning to an object property (Document.Author) which is possible only if it allows write access in the installed version of GroupWise.

Have you tried calling the following method before assigning Creator to Author?

  DocBid.Refresh

I hope this helps.

Regards,
Advansys Support

[Support 1]

L.P.,

The error “Not yet implemented” comes from GroupWise (the ObjectAPI to be precise) – Formativ simply captures and displays the error.

I am not sure why you are seeing this error. According to the online documentation of FieldDefinition, FieldID is available in “GroupWise 5.5 and later”.

Have you tried to call the following method – before enumerating the library field definitions?

  Library.Refresh()

You may find the answer to this error, and the strange ‘ghost’ and ‘old’ names among the support options offered by Novell.

I hope this helps.

Regards,
Advansys Support

[Support 1]

L.P.:

Thank you for your suggestions.

John:

It appears that the workstation (which does not have the NetWare client installed) is not logged in to eDirectory. Have all relevant settings in the Formativ utility (in the Windows Control Panel) been set appropriately? I mean the settings on the Protocols and LDAP tabs.

If the problem continues, could you send the Formativ configuration (see below) from this workstation? Please send this information to support@advansyscorp.com .

You can obtain the configuration by selecting Help | About Formativ… from the GroupWise main menu. When the About Formativ dialog appears, go to the Configuration tab and click the button Copy to clipboard. Then paste the text into your email (or save it to a plain-text file and include it as an attachment).

Regards,
Advansys Support

[Support 1]

Andre,

We sent the information to your email address in the Advansys Support Forums members database, but we received a notification of “Permanent Delivery Failure”.

Could you email your request to support@advansyscorp.com please?

Regards,
Advansys Support

[This message was edited by Support 1 on June 27, 2006 at 08:50 PM.]

[Support 1]

Thank you for your enquiry.

We have not seen this problem reported previously. Other customers who have deployed Formativ on Citrix (or Windows Terminal Services) are using the product successfully.

I notice (in a more recent post) that you have requested more information on how to deploy on Citrix. This information will be sent by direct email.

If you are still having problems, please provide more details on:

quote:

---

We are using Romaing Profiles and so the ‘Local Settings’ are newer in an Profile. Unfortunately Formativ Message Saver Pack 2.0 saves his config and ohters in a Subfolder of ‘Local Settings’.

---

Regards,
Advansys Support

[Support 1]

The featured topic mentioned previously has been updated to be more general: you should follow the directions for a2gofinder.exe as well as for a2goindexer.exe.

If the problem remains after trying the suggestion above, could you translate the text of the error into English, please? What is the full path to a2gofinder? Also, what version(s) of the .NET Framework is/are installed?

Regards,
Advansys Support

[Support 1]

Thank you for your enquiry.

Have you installed Microsoft Internet Explorer 5.01 or above on the affected machine? This is a requirement specified in the user manual for the Viewer.

Which version of Archive To Go do you have? There was a defect which caused this error in an early version of the Viewer, now fixed in version 1.0.0.6.

Regards,
Advansys Support

[Support 1]

To resolve this issue, please see the featured topic Running Archive To Go from a Network drive.

Regards,
Advansys Support

[Support 1]

While editing (designing) a form, you can adjust properties of a form’s horizontal and vertical scrollbars (HorzScrollBar, VertScrollBar) in the Object Inspector. By default, form scrollbars will appear automatically, ie. whenever a control on the form is positioned outside (or overlapping) any edge of the form. Example controls are Label, EditBox and Button.

However, I would suggest that you avoid designing a form which relies on scrollbars to provide access to ‘out of bounds’ controls. This honours the user interface design guideline of minimizing the number of steps a user must take to achieve something. A useful rule of thumb is to optimize the design for an ‘average’ screen resolution of 1024 x 768, but also to support lower (800 x 600) and higher (1280 x 1024). The form should be tested with each screen resolution.

One possibility is to allow the user to resize or maximize the form:

  Form1.BorderStyle = bsSizeable

unless the form is really a (fixed size) dialog box:

  Form1.BorderStyle = bsDialog

This option can be used effectively in combination with the Align property of each control on the form. If, for example, a form has a number of Label and EditBox controls, all of them could have Align = alTop; then regardless of the form size, all controls align automatically, from top to bottom, to occupy the available horizontal space. Consider using Panel or Bevel controls to provide spacing between other controls.

Note that you may need to take into account the variation when the Windows display is set to use large (or small) fonts.

You may find it necessary to separate a user interface into two (or more) forms in order to honour these guidelines.

More information on the design of forms is available in the help file which documents the Standard and Additional tabs of the Component palette. Search the index for “user interface” then navigate to “Managing layout”.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Thanks for the clarification.

We have received the log, and will continue this discussion by direct email.

Regards,
Advansys Support

[Support 1]

Simon,

Unfortunately we have no experience with the tool Dynamic Local User Policy.

quote:

---

After successful Netware login [Dynamic Local User Policy] creates a Windows user account with Administrator rights using the Netware credentials

---

What do you mean by “using the Netware credentials”?

It appears that this problem has to do with the rights assigned to the new user. The fact that Formativ does not appear in GroupWise suggests that the new Windows user account is limited in some way (ie. not a power user/Administrator).

The following information about the GroupWise C3PO architecture may help. Formativ is a custom third-party object (C3PO), ie. add-on for GroupWise.

The GroupWise C3PO architecture uses the Windows registry hive HKEY_LOCAL_MACHINE to store user specific C3PO settings.

The only practical problem is likely to be if your users do not have the appropriate rights to write to HKEY_LOCAL_MACHINE. This could be overcome by providing those rights to every user, or by installing a master GroupWise/Formativ configuration, including applets, for a special user who does have the appropriate registry rights. Alternatively, it could also be possible to extend the registry by manually creating the required entries under HKEY_LOCAL_MACHINE.

Upon startup, Formativ tests read/write access to the following registry key area:

HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypes

Read/write access to this area is required for registering GroupWise events and other client integrations which may be used by Formativ and Formativ applets. This is a standard GroupWise third party integration requirement. Read/write access is usually required beyond initial administrator installation because applets dynamically register for the events at the time of their first execution.

A GroupWise integration registry entry looks like:

HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypesGW.MESSAGE.MAILAdvansys.formativEventsGW#C#REPLY

and in this case, it indicates that an applet or C3PO has registered to be notified when a Mail message REPLY event is activated (ie. a user replies to a Mail message).

If Formativ cannot write to this area, applets cannot register for events or other client integrations (toolbars, menus).

Possible Solutions

OPTION (1) Modify ‘limited user’ profile security to allow additional registry access.

• allow read/write access to ‘HKEY_LOCAL_MACHINESOFTWARE’ hive; or
• allow read/write access to ‘HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypes’ hive.

OPTION (2) Create HKEY_LOCAL_MACHINESOFTWARE entries during main Administrator installation.

The admin install should create automatically:
HKEY_LOCAL_MACHINESOFTWAREAdvansys Corporationformativ1.0

The admin install should create automatically some settings in:
HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypes

For applet solutions, when in Administrator mode, you would need to install EVERY applet which the limited user will need to run. This will ensure all the appropriate entries are written to:

HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypes

You can then choose to replicate this registry key hive to other machines which need to run the same applets.

You will need to repeat OPTION (2) each time you add an applet which uses a GroupWise client event that is not already registered.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Formativ Runtime does not require the NetWare client to be installed. You do not need to install the Schema Wizard snap-in to use Formativ.

Formativ applets do not need the NetWare client to access the GroupWise AddressBook object.

How do you intend to make “calls to e-directory”?

Regards,
Advansys Support

[This message was edited by Support 1 on June 13, 2006 at 10:52 PM.]

[Support 1]

You can verify whether resources in your GroupWise environment can be viewed in Enterprise mode as follows.

Install the following Advansys products which integrate with the GroupWise client:

• Formativ Runtime
• Enterprise Proxy

Upon installation, both of the above products are available for a 30-day trial.

When you start the Enterprise Proxy solution (click the new icon on the GroupWise toolbar), a dialog will appear. It lets you select the Domain of interest and shows the objects defined for that Domain in a tree view (Post Office, User, Distribution List, Resource).

If Resource objects are displayed in the tree view, then this proves that they can be viewed in Enterprise mode in your environment.

Please let us know how you get on.

Regards,
Advansys Support

[Support 1]

We have received your email, thank you.

Information about obtaining Message Viewer 2.0 has been sent to your email address.

Regards,
Advansys Support

[Author]

Replies