Import DB2 Database

With Scriptoria, you can import DB2 database objects including defaults and check constraints that contain DB2 functions, primary, unique and foreign keys, indexes, and data. For DB2 databases created using Scriptoria, Auto-Numbers, cascade relationship, check and default triggers are also imported.

Object Type Selection

All DB2 Tables displays all DB2 tables for the listed schema.
Migrated DB2 Tables displays only DB2 tables in the current schema with corresponding MS-Access tables.
Schema:
 
Choose the schema that contains the DB2 tables you wish to import. All DB2 tables for the chosen schema are listed.

DB2 Table Selection:

Select the DB2 tables you wish to import. You can highlight one or more entries and press the smaller arrows to select and de-select entries.
Click the Import Options tab to select the location of the Access database that will contain the imported or linked DB2 tables. If no tables are contained in the current Access database, the path to the “.mdb” file is supplied by Scriptoria.
 
Press the Link button to create ODBC linked tables, for the selected DB2 tables, in the current Access database. Unique Access table names are ensured by Scriptoria.
 
Press the Import button to create Access table definitions (and optionally relationships) from the selected DB2 tables. Note that if a database other than the current Access database location is chosen, if it exists it is deleted and then a new (empty), like named database is created.
 
All DB2 column data types are retained unless overridden using "Assign Individual Column Data Types".
Note that Scriptoria creates special Access properties for any DB2 features or properties not supported by Access. For example, if an index is "Clustered", this information is saved in Access. The "Clustered" property included when Scriptoria generates the DB2 index definition. See for DB2 to Access conversion details.
Import Form: