Upgrading from OpenROAD 4.0 or 4.1
Overview
OpenROAD 4.0 was a Microsoft Windows-only interim release that delivered a significant change in the user interface. OpenROAD 4.1 was a full release across Microsoft Windows and supported UNIX platforms at the time it was released. If you are upgrading from OpenROAD 4.0 you may follow the same guidance given in this chapter for OpenROAD 4.1.
The recommendations in this chapter are based on extensive practical experience of 4.1 conversions and have two objectives:
• To ensure that your upgrade is successful the first time
• To minimize time and effort required to upgrade
Upgrading OpenROAD 4.1 to any release prior to OpenROAD 6.2 is straightforward and inexpensive, provided the upgrade is properly prepared for and carefully executed. In most cases all that is required is the automated correction of known upgrade issues covered later in this chapter. In other cases, minimal code changes should suffice.
Upgrading from OpenROAD 4.1 directly to OpenROAD 6.2 is not recommended because the process is irreversible. To illustrate, consider the following procedure:
1. Export an application from OpenROAD 4.1.
2. Import the application into OpenROAD 6.2.
3. Export the application from OpenROAD 6.2.
4. Import the application back into OpenROAD 4.1.
The application is unintentionally corrupted by this process. For example, all button labels in the application are now missing. Unless a backup of the original OpenROAD 4.1 exported application was preserved before importing it into OpenROAD 6.2, the changes are irretrievably lost. This is why Actian Corporation strongly recommends that you upgrade OpenROAD 4.1 applications to OpenROAD 5.1 as an intermediate step before moving the applications to OpenROAD 6.2. Then the following procedure can be performed without corrupting the application:
1. Export an application from OpenROAD 5.1 to XML.
2. Import the application into OpenROAD 6.2 from XML.
3. Export the application from OpenROAD 6.2 to XML.
4. Import the application back into OpenROAD 5.1 from XML.
Note: To preserve the integrity of the application through the export and import process, you must export and import using XML, a feature introduced in OpenROAD 5.1. If you use the original proprietary import/export technique to move an application from OpenROAD 5.1 through OpenROAD 6.2 and then back to OpenROAD 5.1, the application will be corrupted as mentioned in the first procedure. For more information, see "XML Import and Export" in the Workbench User Guide.
This chapter focuses on the known issues specific to upgrading from OpenROAD 4.1 to any version prior to OpenROAD 6.2 and their resolution. If your intent is to ultimately move from OpenROAD 4.1 to OpenROAD 6.2, you should break the upgrade process into two parts:
• Part 1: Upgrade from OpenROAD 4.1 to OpenROAD 5.1 (this chapter).