How to migrate from the 32-bit version of Reliance 4 or Reliance 5 to the 64-bit version of Reliance 5

July 3, 2026

The main benefit of the 64-bit version is the ability to use all available RAM on the computer (the 32-bit version can use at most 3.7 GB). In practice, this is particularly noticeable in large-scale projects. Another advantage of the 64-bit version is higher speed (performance) when using hashing and encryption functions.

For most standard applications, however, the 32-bit version is fully sufficient and there is no compelling reason to switch to the 64-bit version.

What to watch out for when migrating to the 64-bit version

The decision to migrate to the 64-bit version should always be preceded by a thorough check of system dependencies. Most potential issues during the migration to the 64-bit version arise in connection with database drivers, external programs, and libraries. Please pay attention to the following points.

ODBC database drivers

If your project stores historical data or alarms in an SQL database via the ODBC interface, you must ensure that the 64-bit version of the database drivers is installed. The 64-bit version of Reliance (or any other program) cannot use 32-bit ODBC drivers.

BDE database drivers

It will not be possible to display custom reports that contain components dependent on the Borland Database Engine (BDE). BDE is available only for 32-bit applications.

AMiT devices

Communication with an AMiT device will not work if its model is set to "Not specified". This communication method internally uses the older 32-bit AMiT AtouchX ActiveX library, which the 64-bit version is unable to load. If a specific device model is selected (e.g., Gen2 E+), the AMiT AtouchX library is not used.

OPC DA devices

If your project uses OPC DA servers to communicate with subordinate systems, communication may not work because these servers are often 32-bit applications. Although communication between a 64-bit client and a 32-bit OPC DA server is technically possible, it may not work in some cases.

External libraries and add-ons

If the project uses third-party libraries, you must ensure that 64-bit versions of these libraries are available. This may include, for example, visual components for IP cameras or ActiveX controls embedded in visualization windows. Pay special attention to non-visual COM objects created from scripts (using the CreateObject function). If a script attempts to instantiate a 32-bit application or library, the 64-bit version of Reliance will fail to create the instance. In such cases, you must obtain a 64-bit version from the vendor or replace the application or library with a more modern solution.

IMPORTANT:

If, after performing the above review, you find that your project relies on 32-bit elements that cannot currently be replaced or updated, you will need to continue running the project in the 32-bit version of Reliance. When migrating from Reliance 4, we recommend using the 32-bit version of Reliance 5. We recommend switching to the 64-bit version only after you have found a replacement for these 32-bit elements.

Migrating to the 64-bit version of Reliance 5

1. Backing up the project

When migrating from Reliance 4 to Reliance 5, the first step is to create a backup of the visualization project. You can easily generate this backup using the Back Up Project Wizard directly in the Reliance 4 Design development environment.

Warning: Opening the project in Reliance 5 Design triggers an irreversible conversion of the project files. After this conversion, the project can no longer be opened in Reliance 4.

2. Uninstalling the 32-bit version

If you are migrating from the 32-bit version of Reliance 5, you can uninstall it. If you choose not to do so, it will be removed automatically during the installation of the 64-bit version. A single computer cannot have the 32-bit and 64-bit versions of Reliance 5 installed simultaneously. This operation does not remove any Reliance projects or settings from the computer.

3. Installing the 64-bit version

Install the 64-bit version of Reliance 5 in the usual way. All existing licenses will remain valid after the installation — both licenses stored in a hardware key and those stored in a software key. Migrating from the 32-bit to the 64-bit version of Reliance has no impact on the licensing method or on the validity of the license.

4. Checking the project

Open the project in Reliance 5 Design and run project diagnostics. Diagnostics can detect issues related to system dependencies. After that, export the project for remote users.

5. Testing the project

Finally, run the project and thoroughly verify all key functions.

You can find additional information related to this topic in the following articles:

Compatibility of Reliance 4 and Reliance 5

How to download, install, and uninstall the Reliance 5 SCADA/HMI system

Tip:

Haven't found what you were looking for? Use this form to inform us about it.

Try the Reliance SCADA system right now!

Try the Reliance SCADA/HMI system on several sample visualizations.

Try the Reliance SCADA/HMI system on several sample visualizations or download the trial version installer to your computer for free.

Download

Try