All PST Directories created prior to version 6.0 of the Princeton Softech products, Archive and the Relational Tools, require a conversion to be compatible with later versions. Additionally, any Optim™ Directory created prior to Optim version 6.2 on an SQL Server database must be converted.
Use the Configuration program to convert Optim Directories and objects. After the Conversion Process, your “old” PST Directory and objects remain intact and can still be used with the Optim products.
PST Directory objects created using version 5.x of Archive or the Relational Tools must be converted into a format suitable for use with version 6.0 or later. Use the Conversion Process in the Configuration program to migrate objects from an old (5.x) PST Directory to a Directory compatible with version 6.0 or later.
You can convert and migrate the following objects: Access Definitions, Table Maps, Column Maps, Column Map Procedures, Primary Keys, DB Aliases, Relationships, Calendars, Currency Definitions, Storage Profiles, process requests, Archive File Directory entries, and File Access Definitions.
The Conversion Process consists of three steps, which must be completed in the order listed.
If you have upgraded your DBMS, or if imported DB Aliases reference a DBMS version that is no longer supported by Optim, you must run the Update the DBMS Version for a DB Alias configuration task after converting the PST Directory.
PST Directory tables created with the Princeton Softech product versions 6.0/6.1 in an SQL Server database must be converted to accommodate Unicode support in later versions of Optim. The Directory conversion process will copy data in 6.0/6.1 Directories to new Directory tables. The new and old Directories will have the same name and PST object definitions. After the Directory is converted, you can still use the old Directory tables with the Princeton Softech product versions 6.0/6.1, or you can drop the 6.0/6.1 Directory.