With the GRT shell open and the Values tab selected, double click the migration object and find the sourceConnection object. Click this item and its parameters and the values of those parameters will be exposed in the frame beneath the Globals tree. The parameters are as follows:

Open the Lua script that you generated during migration and find the -- Set source connection line. Immediately below this line is the code that defines the source connection of the schema that is being migrated.

The names of the parameters of the source connection in the Lua script should match the parameters shown in the frame below the Globals tree (though they do not appear in the same order). The value shown for the _id parameter is the value created by the newGuid method of the grt object. The Universally Unique Identifier (UUID) of the driver show in this frame should match the value shown in your script.

The name is the name of the variable being created by the Lua script.

In the Values tab both the modules and parameterValues items show as objects of the dict type.

Click on modules to see the modules used during migration. The MigrationModule has a name specific to the migration source schema. If you are migrating from Access, for example, it is called MigrationAccess. Click on parameterValues and see the parameters you supplied for connecting to the source schema.

Below the -- set struct and types line find the definition of the data types used so far. A sourceConnection is a struct derived from the db.mgmt.Connection structure. modules and parameterValues are both strings.

The parameters and the modules used for a targetConnection are shown beneath the --Set target connection line. After examining a sourceConnection you should quickly be able to understand a targetConnection. The same applies to the structs and data types used by the targetConnection.