Many Access applications use multiple databases (mdb files) to separate table data from one or more application front-ends. These applications require special handling.
Use the Performance Analyzer (PA) on each database. Note that suggestions for creating indexes and relationships on “linked tables” must be implemented manually. Although the PA has an automated “Optimize” feature, changes to linked tables are not updatable and therefore not implemented by the PA.
Migrate the Access database that contains the actual (not linked) tables first. Load Scriptoria and use “Assign Object Names” (Options | Assign Object Names menu item) to modify the DB2 names Scriptoria assigns with more meaningful ones if necessary.
Use the database containing the actual (not linked) tables to create the target DB2 database. Note that only the actual database can be used to create relationships.
Open the database(s) containing the linked tables and load Scriptoria. When Scriptoria assigns DB2 table and field names for Access linked tables, it uses the names you assigned in step “2.” above.
For Access databases that contain both linked and local tables; if you wish to migrate the local tables, you can first assign meaningful DB2 object names and then select only the local tables for migration by Scriptoria.
Use Scriptoria to create Access/DB2 applications (see Create DB2 Application) for each database. Note that table links are created only for those Access tables where DB2 tables exist (have names that match the ones assigned in the Scriptoria repository).