Mapping Issues
See Also
General
-
The exact values for all the Repository 1.0 database fields are copied over.
-
The new Repository 2.0 database fields, which take the form Z_???_Z, are treated as follows:
-
Those marked NULLABLE have the value NULL inserted.
-
Those marked NON NULL have 0 as their value.
-
All the Z_VE_Z fields are set to the constant VERINFINITY (hex 7fffffff).
Objects — General Principles
-
Inserting the objects requires adding entries to RTblVersion table, where the IntID will correspond to the RTblObject's IntID.
-
For the RTblVersion table, the columns Z_BranchID_Z and Z_VS_Z will conform to the above standards.
Relationships — General Principles
-
For the table RTblRelships in the Repository 2.0 database, the values of the following columns are set as follows:
Z_OrgBrID_Z = 0
Z_OrgVS_Z = 0
Z_DstBrID_Z = 0
Z_DstVE_Z = 0
Z_DstVS_Z = 0
Z_OrgVE_Z = VERINFINITY
Properties
-
For the table RTblPropDefs in the Repository 2.0 database, the following columns are set as follows:
Z_VS_Z = 0
Z_VE_Z = VERINFINITY
Exceptions to the Rule
-
For the table RTblVersions, both Z_PredBrID_Z and Z_PredVer_Z are set to VERINFINITY
Information Model Tables
-
The Migration Wizard adds the columns Z_VS_Z, Z_VE_Z, and Z_BranchID_Z.
-
The following columns are set as follows:
Z_VS_Z = 0
Z_VE_Z = VERINFINITY
Z_BranchID_Z = 0
Information Model Keys
The Information Model's primary keys are extended to include Z_VS_Z, and Z_BranchID_Z.
Information Model Indexes
Indexes are checked. Non-unique indexes are recreated. Unique indexes are displayed or logged for user intervention.
JET Compaction
After the migration is complete, the ODBC driver is used to compact the new MDB.