Upgrading to BlueZone 7.1

There are two methods to upgrade BlueZone: upgrade to a new major version or upgrade within the same major version.

• You can upgrade from any earlier major version of BlueZone to BlueZone 7.1. For example, you can upgrade from version 5.2 to 7.1. BlueZone 7.1 is installed as a new product, and it can run side-by-side with any earlier major version of BlueZone.
  The upgrade procedure is identical to installing a new installation. Refer to Installing BlueZone 7.1 for the upgrade procedure.

  If you do not want the old version installed, you can uninstall the old version. Refer to Uninstalling BlueZone for more information.

• If a patch is available, you can upgrade within the same major version. For example, you can upgrade from version 6.1.1 to 6.1.2. If a patch is not available, the \Patches folder will be empty.
  As the BlueZone administrator, you can push the patch file out to your users. This allows your users to upgrade with a single file.
  1. Download new BlueZone CD image.
  2. Open the BlueZone Desktop folder.
  3. Open either the win32 folder (if you have BlueZone 32-bit installed) or the x64 folder (if you have BlueZone 64-bit installed).
  4. Open the Patches folder.
  5. Perform one of the following options:

     • To upgrade a single installation, double-click the BlueZone Patch 7.1.x.xxxx.exe file. The wizard guides you through the upgrade procedure.

     • To push the patch upgrade out to your users, distribute the patch file to your users, and instruct them to run the file.

     Note:

     If installing 64-bit BlueZone on a machine that currently has a different version of 32-bit BlueZone installed, you should first uninstall the 32-bit version of BlueZone before installing 64-bit BlueZone. If a 32-bit build of BlueZone is uninstalled after a different version of 64-bit BlueZone is installed, then it will remove the global version-independent object ProgIds from the Registry, and will require the 64-bit objects to be re-registered before they can be used again with 64-bit BlueZone.

     The same applies when installing 32-bit BlueZone on a machine that currently has a different version of 64-bit BlueZone installed. You should first uninstall the 64-bit version of BlueZone.

     This issue only occurs when using the global version-independent ProgIds in scripts, VBA macros, custom applications, etc. to invoke BlueZone automation objects using late binding.

     This issue does not occur when installing both 32-bit and 64-bit builds of BlueZone of the same version, any order can be used to install and uninstall, or both bitnesses can be installed.