Clicking the (Step 3) Create Table button automatically generates the table creation SQL code and sends the commands to the destination database to create the table. The Fieldsize information gathered in Step 2 is used to automatically size VARCHAR columns to the correct size, based upon the data within the source FileMaker database table. Columns containing more than 255 characters of text are converted into the appropriate large text/memo/CLOB column type for the destination database.

The Table Creation Details button in the upper right corner of the Step 3 button opens the Table Creation Details window.

[FileMaker 7+ Repeating Fields Processing Step]

When clicking the (Step 5) Convert Data button, FmPro Migrator generates ScriptMaker repeating fields data conversion scripts and puts these scripts onto the clipboard. These repeating fields scripts convert the data within each repeating field into a TAB delimited format within the first iteration of the repeating field and only need to be run once for each source database table. FmPro Migrator will insert each iteration of a FileMaker repeating field as a new record within the repeating fields table.

This step is not required when processing repeating fields for FileMaker 5, 5.5 or 6.0 database files.

[Repeating Fields Processing Step]

Clicking the (Step 6) Create Table (Repeating Fields) button automatically generates the table creation SQL code and sends the commands to the destination database to create the table. The Fieldsize information gathered in Step 2 is used to automatically size VARCHAR columns to the correct size, based upon the data within the source FileMaker database table. Columns containing more than 255 characters of text are converted into the appropriate large text/memo/CLOB column type for the destination database.

The Table Creation Details button in the upper right corner of the Step 6 button opens the Table Creation Details window.

[Repeating Fields Processing Step]

Clicking the (Step 7) Transfer Data (Repeating Fields) button transfers the repeating fields data for all of the database records from the FileMaker database to the destination database via an ODBC connection (or a direct connection for: MySQL and PostgreSQL).

[Optional Image Export Step]

The Image Export button saves the contents of FileMaker container fields into files on the local hard disk. Images are automatically transferred via ODBC to each destination database except FileMaker 7+, so this step is optional.

After clicking this button, the Image Export dialog is displayed for selecting the container field and filename field to be used when exporting the data.

FileMaker 5/6 databases support JPEG image export from container fields.
FileMaker 7+ databases support the following 22 data types for export: EMBO, EMF+, EPS, FILE, FPix, FORK, GIFf, JPEG, JP2, META, METO, moov, PDF, PICT, PNGf, PNTG, qtif.SGI, snd, TIFF, TPIC, XMLO, and 8BPS.

The Table Details Window provides fields for changing migration parameters on a table by table basis. The Migration Notes field is one of the fields written to the summary report produced for the migration process.

The lock icon locks changes to the destination field type for each field. The destination field type is normally set automatically during the Create Table steps, but this value can be locked after manual changes are made. This feature is useful whenever column types are overridden with the buttons which set Numeric Fields to Varchar, Date Fields to Varchar or Varchar to TEXT.

Clicking the Field Details icon or double-clicking a field in the list of fields, opens the Field Details Window.

The Field Details Window provides fields for changing field parameters on a field by field basis. The destination field type information is set automatically during the Create Table step.

FmPro Migrator is usually able to figure out the primary key field automatically by looking for any field which has Not Empty and Unique validation parameters set within the FileMaker database. But if these values aren't set within the FileMaker database, it is sometimes necessary to manually check or uncheck the Primary Key icon (yellow key symbol) to indicate that a field is a primary key.