Autodesk 00128-051462-9310 - AUTOCAD 2008 COMM UPG FRM 2005 DVD, User Manual

Page: 2214 / 2268

Migrating Your Database Modifications
AutoCAD Architecture provides default Microsoft
®
Access databases for detail components and keynotes. If you have
modified either of these databases in a previous release (or created your own databases using the same schema), you
can migrate your modifications to the corresponding database in the current release using the Detail Component/Keynote
Database Migration utility. Accessed from the CAD Manager menu, this utility compares the modified database (the
source) with its counterpart in the current release (the target) and updates the current database to reflect your
modifications.
IMPORTANT Beginning with AutoCAD Architecture 2008, the US detail component and keynote databases supplied with
the software use the CSI MasterFormat 2004 standard. Using the Detail Component/Keynote Database Migration utility to
migrate your customizations from a database that uses the CSI MasterFormat 95 standard (as in Autodesk Architectural Desktop
2007 and previous releases) is not supported. The utility will not properly migrate custom records from the older database
and may errantly overwrite records in the new database with MasterFormat 95 data. If you want to use a MasterFormat 95
database with the current release of AutoCAD Architecture, you can load it as described under
“ Adding a Detail Component
Database to Available Databases ” on page 1948 or “ Adding a Keynote Database ” on page 1973 . Note that the older database
must be located with the previous release content and must maintain that content folder structure to function properly. An
older detail component database will not function with 2008 US details content. Likewise, an older keynote database will not
automatically keynote 2008 US details content; it will only keynote detail components inserted using previous version details
or details in previous version drawings. The Detail Component/Keynote Database Migration utility can still be used to migrate
records from one CSI MasterFormat 95 database to another. Note also that using the Database Migration utility to update
an older database with data from a current-release database is not supported. The utility is designed only for migrating
modifications in the other direction; that is,
from the older database to the database in the current release.
The migration utility operates according to the following assumptions and rules:
■
Both the source and target databases must be of the same type (either Component or Keynote), as identified by
the first record in their Fingerprint tables. (For more information on the tables and records included in these
databases, see “
Customizing and Adding New Content for Detail Components ” on page 2143 and “ Keynote Database
Schema ” on page 1980.)
■
Both the source and target databases must use the same version of the CSI MasterFormat standard.
■
If a table in the source database has no counterpart in the target database, the table and all its records are added
to the target database.
■
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 migrated; 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.
2174 | Chapter 53 Migrating Detail Component and Keynote Databases