Loading ...
Loading ...
Loading ...
â– Tables of the same type (as identified by their ID fields) are compared, and
source records that differ from their counterparts in the target database
(or have no counterparts) are processed as shown in the following matrix.
No corresponding target
record exists
Corresponding target
record exists
source record added to target
table
source record overwrites
target record
Modified field in
source record = true
source record added to target
table
source record is not mi-
grated; target record is not
changed
Modified field in
source record =
false
NOTE If you have added a detail component size table or keynote of your
own in the previous release, and it happens to have the same table name or
keynote key as a new table or keynote supplied in the current release, it will
not be processed by the migration utility, because its ID will differ from its
namesake in the current release. If this scenario seems likely in your case, it is
recommended that you check to see if the name you assigned is present in
the current release. If so, you should change the name of your table or keynote
key before running the migration utility.
â– If a source database record has been modified using the Detail Component
Manager or the Keynote Editor, its Modified field value is set to true
automatically, and the record will overwrite the corresponding record in
the target database, or be added to the target database if there is no
corresponding record present.
â– If a source database record has been modified using Microsoft
®
Access
directly, and the Modified field value was not set to true manually, the
record will be added to the target database if there is no corresponding
record present.
â– The migration utility processes only tables and records as described above;
it does not migrate any associated XML or DWG content files, nor does it
migrate default values specified for particular fields in tables. Preserving
such information requires manually updating the target database.
NOTE If migrated records were created using Microsoft
®
Access directly (rather
than through the Detail Component Manager), and they do not have a valid
record ID (equal to or greater than 100000), it may result in a conflict with records
in the target database.
Migrating Your Database Modifications | 3965
Loading ...
Loading ...
Loading ...