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 databases that contains the actual (not linked) tables first. Load Scriptoria and use “Assign Object Names” (Options | Assign Object Names menu item) to modify the Oracle names Scriptoria assigns with more meaningful ones.
Use the database containing the actual (not linked) tables to create the target Oracle 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 Oracle 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 Oracle object names and then select only the local tables for migration by Scriptoria.
Use Scriptoria to create a new Access application that uses Oracle as the back-end. (see Create Oracle Application) for each database. Note that links are created only for those Access tables where Oracle tables exist (have names that match the ones assigned in the Scriptoria repository).
For Access applications that use linked ODBC data stores from existing Oracle applications, the assigned Access table name must be changed to refer to the actual table names. Use the Global Assign Table Names feature.