/ Forums / Advansys Formativ / Formativ Runtime / Changing the Runtime Installation Directory

  • Creator
    Topic
  • #3699
    Anonymous

    I have two problems which might be related:

    1. We need to install Formativ Runtime locally on several workstations, along with an applet that disables certain menu items in the GroupWise toolbar. It works flawlessly on only one station, but not on the others. The applet will output test messages, indicating that we are pointing to the correct directory, but it will not execute the line of code (sample shown below) that disables the menu items:

    if groupwise.envversionname = “6.5.1” or groupwise.envversionname = “6.5.2” or groupwise.envversionname = “6.5.2” then

    Call GroupWise.RemoveMenuItem(“GW.CLIENTFileImport Documents…”)

    end if

    Restarting the client and rebooting the system have no effect.

    Any ideas on why this might be happening?

    2. We need to install Formativ locally in a directory other than the default one determined by the installer (C:Program Files etc) to troubleshoot the problem in 1.

    Is there a way to specify a different target directory for the installation of the Formativ Runtime, and not just the BACKUP files?

    NOTE: We have installed Groupwise locally, in a directory other than C:Program Files. Is it possible that Formativ cannot locate the Groupwise menu items properly, and therefore cannot disable them?

    Any help would be appreciated.

  • Author
    Replies
  • #5867
    Support 1a
    Participant

    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

    #5861
    Anonymous

    I outputted a messagebox AFTER checking the version name and on the workstation that doesn’t work, and it reads “Groupwise version 6.5.2”. So the applet is attempting to execute the block of code inside the IF statement. For some odd reason, it skips the lines that disable the menu items. Am I missing an environment or registry setting of some kind?

    Could you please tell us how to specify another target directory for the Formativ Runtime installation?

    Thanks.

    #5863
    Support 1a
    Participant

    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

    #5866
    Anonymous

    It turns out we forgot to enable Formativ in the Formativ Applet (from Control Panel). We had “Formativ Runtime” enabled, but not “Formativ” because we wanted to remove the “Formativ Help” menu items from GroupWise.

    Why do both of these options need to be enabled in order for our applets to run, and what exactly is the difference between these two when it comes to running applets?

    #5862
    Support 1a
    Participant

    I’m guessing you are referring to the ‘Formativ Runtime’ option under ‘Enable/Disable Features’ and ‘Formativ’ under ‘Settings’ on the local config tab.

    The former completely disables the loading of the main component of Formativ. It is used to physically stop Formativ from being loaded with GroupWise.

    The ‘Formativ’ setting on the local config tab doesn’t stop Formativ from being loaded – it just stops most features from working. This setting is really a hang over from the eDirectory management side of things, where eDirectory can be used to stop a user from loading and running applets. However, Formativ still needs to be loaded so that it can communicate with eDirectory – hence the two different settings.

    You should have both the settings enabled to run applets.

    The more recent versions of Formativ 1.6 (and version 2.0) let you disable the Formativ Help menu items via a registry key:

    HKEY_CURRENT_USERSoftwareAdvansys Corporationformativ1.0Settings
    Value Name: ‘Add Help Menu Items’ (DWORD)
    Value: 1 = Add Items, 0 = Don’t add items

    Regards,

    Advansys Support

    #5865
    Anonymous

    Thanks for the info.

    As for disabling Formativ Help, we are still unable to disable it.
    We are using Formativ 1.6 (2003)

    This is what’s in the Registry:

    Value Name: Add Help Menu Items
    Value: 0

    Could you please clarify what (DWORD) is?

    #5860
    Anonymous

    Okay. We have the value type set to DWORD and it still doesn’t work.

    We must not have the most recent version of Formativ 1.6 then?

    Are there any special considerations to make when working with the French Version of Groupwise?

    #5864
    Support 1a
    Participant

    The Help Menu Removal feature should not be related to the language version of the client.

    I would suggest you download and install the latest version of Formativ Runtime from http://www.advansyscorp.com/formativ_download_16.htm

    Please let me know if you still have problems.

    Advansys Support

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.