Known 5.1 Issues to Resolve
There is a known issue when upgrading from OpenROAD 5.1 to the current version that involves copying or creating database connection profiles. When you upgrade from OpenROAD 5.1 to OpenROAD 11.2 on newer 64-bit Windows platforms, the path to database connection profiles changes. You must copy OpenROAD 5.1 profile files to the OpenROAD 11.2 directory or recreate the profiles when you start Workbench.
You may also need to migrate EntryFields.
Copy Profiles to Connect to the Same Ingres Instance
If you are accessing the same Ingres instance in OpenROAD 11.2, you may copy the database connection profiles from the OpenROAD 5.1 storage location to the OpenROAD 11.2 location.
Note: Close OpenROAD before copying the files.
Copy files from the OpenROAD 5.1 location
For Windows Server 2008, Windows Vista, and Windows 7:
%ALLUSERSPROFILE%\OpenROAD\Profiles
For Windows Server 2003 and Windows XP:
%ALLUSERSPROFILE%\Application Data\OpenROAD\Profiles
To the OpenROAD 11.2 location
For Windows Server 2008, Windows Vista, and Windows 7:
%USERPROFILE%\AppData\Local\OpenROAD\Profiles\installation_ID
For Windows Server 2003 and Windows XP:
%USERPROFILE%\Local Settings\Application Data\OpenROAD\Profiles\installation_ID
Recreate Profiles to Connect to a New Ingres Instance
If you want to connect to a new Ingres instance, at the end of installation or the first time you start Workbench, the OpenROAD 11.2 Startup Assistant will guide you through the process of creating a default database connection profile.
For more information about creating database connection profiles, see "Define a Database Connection Profile" in the Workbench User Guide.
Migrate EntryFields
OpenROAD 6.2 introduces additional settings for the EntryField UseWidestCharacter attribute. OpenROAD 5.1 had two settings for this attribute, TRUE and FALSE. OpenROAD 6.2 has four settings, two of which are migration related:
• UWC_NONE, equivalent to the 5.1 setting of TRUE
• UWC_COMPAT equivalent to the 5.1 setting of FALSE
If you experience EntryFields where the width has grown after being migrated from 5.1, you will need to inspect the value of the UseWidestCharacter attribute and ensure it is set to UWC_COMPAT.
For more information about these new 6.2 settings, see the 6.2 Release Summary or the 6.2 Language Reference Guide.
Last modified date: 12/20/2023