FmPro Migrator Developer Edition Table Consolidation Procedure

8/6/2019 FmPro Migrator Developer Edition Table Consolidation Procedure

1/97

FmPro Migrator DeveloperEdition - Table Consolidation

Procedure


2/97

1 Installation

1.1 Installation Tips 5

2 Step 1

2.1 Step 1 - Import Table Definitions 11

3 Step 2

3.1 Step 2 - Get Layouts 17

4 Step 3

4.1 Step 3 - Get ScriptMaker Scripts 29

5 Step 4

5.1 Step 4 - Import Relationships, TOs, Value Lists and Custom Functions 35

6 Step 5

6.1 Step 5 - Remap Objects 48

7 Step 6

7.1 Step 6 - Create Tables, TOs and Relationships 51

7.2 Step 6 - Create Custom Functions 66

8 Step 7

8.1 Step 7 - Create Scripts and Layouts 72

8.2 Step 7 - Create Value Lists 85

9 Step 8

9.1 Step 8 - Create Import Scripts 91

10 Finishing Up


3/97

10.1 Manual Completion Tasks 96


4/97

Installation

FmPro Migrator Developer Edition - Table Consolidation Procedure - 4


5/97

Installation Tips

This document provides an explanation of the steps required to perform a Table Migration project usingFmPro Migrator Developer Edition.Revision 032/11/2009

Installation Tips

Tip1: Don't rename the FmPro Migrator or FileMaker Advanced executable files on your hard disk. Ifyou want to maintain different versions of these applications, put them into folders containing differentnames. The QuicKeys/WinAutomation scripts look for these two applications by their executablefilenames, and if they are renamed the shortcuts won't be able to find the applications even if theapplications are currently running.

Tip2: On Mac OS X, the operating system generally seems to associate the most recently installedversion of FileMaker Advanced with the application name "FileMaker Advanced". Both AppleScript andQuicKeys can become confused if you have multiple versions of FileMaker Advanced installed on yourcomputer. So if you are reinstalling software, it is recommended that you install the latest version last.You could rename the executable files for older versions of FileMaker Advanced to include the versionnumber, thus insuring that QuicKeys doesn't mistakenly use it when you are running QuicKeys scripts.Renaming older versions of the FileMaker executable will cause problems when running FileMakersupplied updaters.

Tip3: In order for the QuicKeys/WinAutomation shortcuts to find elements within the FileMaker userinterface, the Manage/Define Database window needs to be resized to its smallest horizontal andvertical sizes. Otherwise, the shortcuts won't be able to find the correct locations for clicking on buttonor icons during the automated creation of TOs and Relationships.



6/97

Select Output Directory

FmPro Migrator stores migration information for each project within a SQLite database file namedMigrationProcess.db3. FmPro Migrator needs to know where this file should be stored, prior to startingyour migration project. You can have as many MigrationProcess.db3 files as needed (for instance aseparate file for each project), as long as these files are stored within different directories on your harddisk. This output directory is also used for writing automation scripts, instructions and theFileMakerDB.fp7 template database file.

On the FileMaker tab within FmPro Migrator, click the Browse button, then select an output directory

[If you select an output directory which already contains a MigrationProcess.db3 file, the yellowContinue... button will be enabled so that you can continue working on a previously created project.Otherwise, the MigrationProcess.db3 file will be created automatically when you add the first table toyour migration project.]



7/97


8/97

Select Source and Destination Database Types

Selecting both the Source Database and Destination Database types as FileMaker 7/8/9 triggersFmPro Migrator to enter Table Consolidation mode once the first table is copied from the ClipBoard.

Note: It is important to accurately select the type of Destination Database in order for FmPro Migrator touse the correct QuicKeys or WinAutomation scripts when performing migration tasks. Different versionsof FileMaker have used differing menu options, therefore customized automation scripts are used byFmPro Migrator based upon the database version. The selection of the Source Database is not ascritical, and either FileMaker 7, 8 or 9 may be selected for all Table Consolidation projects.

Convert FileMaker 5/6 Files

FmPro Migrator Developer Edition uses FileMaker Advanced 8, 8.5, or 9 when performing a TableConsolidation project. Open the original (older) files with the newer version of FileMaker Advanced and



9/97

the files will be converted automatically by FileMaker. For the purposes of this documentation, theseconverted files are considered to be the source data files for the project.



10/97

Step 1



11/97

Step 1 - Import Table Definitions

Step 1 - Import Table DefinitionsFmPro Migrator Developer Edition uses FileMaker table definitions copied from the clipboard to createthe tables in the new consolidated database file. These table definitions include all table/field options,validations and calculation formulas required to recreate the tables within a new database file.

Step 1 - Open Define/Manage Database Dialog within FileMaker

Open each source database file within FileMaker Advanced. Select the table within the Define/Manage



12/97

Database dialog, click the Copy button.

Step 1 - Paste Table into FmPro Migrator

On the FileMaker tab of the main FmPro Migrator window, select the "ClipBoard XML" menu item, thenclick the Get Info button.

Export DDR File

After copying the table definition via the Clipboard, export a DDR XML file from each source databasefile. These files will be used to import Relationships into FmPro Migrator later in the migration process.



13/97

Click Continue... Button

Once the first table has been copied into FmPro Migrator, the yellow Continue... button will become

visible. Click the Continue... button to open the Migration Process window.



14/97

Migration Process Window...

Clicking the Continue... button opens the Migration Process window to the Tables tab. The TableConsolidation text in the upper left corner of the window provides a visual indication that FmProMigrator is in Table Consolidation mode.



15/97

The overview of the Table Consolidation process includes:[Step 2] capturing Layouts,[Step 3] copying ScriptMaker Scripts,[Step 4] importing Relationships and Table Occurrences from DDR XML files created for each of thesource database files,[Step 5] Object remapping and layout text search & replace tasks,[Step 6] creation of Tables, Table Occurrences and Relationships, in the new consolidated file,[Step 7] creation of Scripts and Layouts,[Step 8] creation and use of data import scripts to import data from the source database files to the newconsolidated file.



16/97

Step 2



17/97

Step 2 - Get Layouts

Step 2 - Get Layouts

Clicking the Step 2 - Get Layouts button opens the Layouts tab of the Migration Process window.



18/97

You can also click on any of the folder tabs across the top of the Migration Process window to godirectly to that area of functionality.

Step 2 - Layouts Tab



19/97

The Layouts tab provides an interface for managing layouts during a migration project. Layouts can becaptured from FileMaker either one at a time [1] or in batch mode [2], and can be transferred toFileMaker the same way [3],[4]. Search & Replace parameters [5] for layout text can also be specified.

Clicking on a layout in the list displays details for the layout, including a thumbnail version of the layoutimage.

Clicking on a portal displays the portal rectangle on the thumbnail image [6]. The portal details,including Portal Fill, SQL and Portal Titles fields are not used during Table Consolidation migrations.

Step 2 - Layouts Tab - Entering Layout Search & Replace Parameters

Clicking the Layout Search & Replace button displays the dialog for specifying these parameters. Anynumber of Search Text and Replace Text values can be specified in this dialog.

Enter each value, then press the TAB key or Return key to advance to the next cell or row.



20/97

Step 2 - Click Import All Layouts Button

The Import All Layouts button starts the automated process of importing all of the layouts from theFileMaker database which is currently open. Open the first source FileMaker database file which youare migrating, then click the Import All Layouts button.



21/97

Repeat the following steps to import layouts from each of the source database files.

Once all of the layouts have been imported from each source database file, they should be review todetermine if there are any layouts having duplicate names. Manually rename any duplicate layoutswithin the list of layouts. A thumbnail image of each layout and the Display Records From: TO areavailable on the Layouts screen in order to assist the developer when identifying each layout.

Step 2 - Select the DDR XML File

FmPro Migrator needs to read the table occurrence associated with each layout from the DDR XML filewhich was previously exported.

Select the DDR XML file, then click the Open button.



22/97

Step 2 - Click Download QuicKeys Button (Mac OS X) - [1st Time Setup Step]

The Download QuicKeys dialog is displayed by FmPro Migrator on Mac OS X. Click the DownloadQuicKeys button if you don't already have QuicKeys 3.03 (or higher) installed on Mac OS X.

Click this download button even if you do have QuicKeys installed, because clicking this button triggersFmPro Migrator to create the FmPro Migrator QuicKeys Installation.pdf and FmPro Migrator QuicKeysShortcuts - Mac.qkexport files within the output directory. Whenever the QuicKeys Shortcuts have beenupdated within FmPro Migrator, you will need to click on this button in order to extract the latestshortcuts from FmPro Migrator for installation on your computer.

Follow the instructions within the FmPro Migrator QuicKeys Installation.pdf file to import the QuicKeysshortcuts from the FmPro Migrator QuicKeys Shortcuts - Mac.qkexport file into QuicKeys and set up theQuicKeys variables. These QuicKeys shortcuts use 10 QuicKeys variables which must be createdmanually prior to using the shortcuts.



23/97

Step 2 - Automatically Save Layout Changes Preference (MacOS X) - [1st Time SetupStep]

One of the important tasks listed in the QuicKeys Installation PDF file is to set the "Save layoutchanges automatically" option within the FileMaker Advanced Preferences dialog.Select the FileMaker Preferences menu item, (1) click the Layouts tab, (2) click the checkbox to enablethe "Save layout changes automatically (do not ask)" option, then (3) click the OK button.



24/97

Step 2 - Click Download WinAutomation Button (Windows) - [1st Time Setup Step]

The Download WinAutomation dialog is displayed by FmPro Migrator on Windows. Click the DownloadWinAutomation button if you don't already have WinAutomation 1.2.0.622 (or higher) installed onWindows.

Click this download button even if you do have WinAutomation installed, because clicking this buttontriggers FmPro Migrator to create the FmPro Migrator WinAutomation Installation.pdf and FmProMigrator WinAutomation Jobs.zip files within the output directory. Whenever the WinAutomation Jobshave been updated within FmPro Migrator, you will need to click on this button in order to extract the

latest versions of these jobs from FmPro Migrator for installation on your computer.

Follow the instructions within the FmPro Migrator WinAutomation Installation.pdf file to import theWinAutomation jobs from the FmPro Migrator WinAutomation Installation Jobs.zip file intoWinAutomation.



25/97

Step 2 - Automatically Save Layout Changes Preference (Windows) - [1st Time SetupStep]

One of the important tasks listed in the WinAutomation Installation PDF file is to set the "Save layoutchanges automatically" option within the FileMaker Advanced Preferences dialog.Select the FileMaker Preferences menu item, (1) click the Layouts tab, (2) click the checkbox to enablethe "Save layout changes automatically (do not ask)" option, then (3) click the OK button.

Step 2 - Start WinAutomation Console Application (Windows) - [1st Time Setup Step]

The WinAutomation Console application will install and startup the WinAutomation Service the first timeit is launched. You may close the WinAutomation Console after importing the WinAutomation jobs.



26/97

Step 2 - Click the Copy All Layouts Button (2nd Time)

Select the DDR XML file, then click the Ok button on the Batch Import dialog.

FmPro Migrator will then use the QuicKeys/WinAutomation shortcuts to drive the FileMaker user



27/97

interface in the same manner as a user would use the program to copy each of the Layouts into FmProMigrator.

Step 2 - Controlling Batch Capture Mode

FmPro Migrator takes over the computer's keyboard/mouse when controlling FileMaker to capture orcreate layouts in FileMaker. If you need to cancel the process while it is running, click the Done button

at the bottom of the Layouts tab.



28/97

Step 3



29/97

Step 3 - Get ScriptMaker Scripts

Step 3 - Get ScriptMaker Scripts

Click the Step 3 button to copy all of the ScriptMaker scripts from each FileMaker source database.



30/97


31/97

then be copied to the Clipboard [2] and pasted back into FileMaker Advanced.

Scripts can also be viewed within FmPro Migrator by clicking each script and viewing the text version ofthe script within the Script Text field [3]. Duplicate or unneeded scripts can also be deleted by selectingthe scripts and clicking the Delete button [4].

Step 3 - Copy ScriptMaker Scripts From FileMaker to ClipBoard

Within FileMaker Advanced, open the ScriptMaker window, select all of the scripts and select Copyfrom the Edit menu.



32/97

Step 3 - Paste ScriptMaker Scripts From ClipBoard Into FmPro Migrator

Click the Add Scripts from ClipBoard button to paste the scripts into FmPro Migrator.

You will perform this task for every source database file which contains scripts to be added to the



33/97

destination database file.



34/97

Step 4



35/97

Step 4 - Import Relationships, TOs, Value Lists and Custom Functions

Step 4 - Import Relationships, TOs, Value Lists and Custom Functions

FmPro Migrator imports Relationships, Table Occurrences, Value Lists and Custom Functions by



36/97

reading the contents of the DDR XML file for each source database file.

Click the Step 4 - Get Relationships button or click on the Relationships tab.



37/97

Step 4 - Relationships Tab

The Relationships tab provides an interface for managing the relationships which will be migrated intothe consolidated database file.It won't generally be necessary to make changes on either the Relationships or TOs tab when



38/97

performing a Table Consolidation project. But changes made on both of these tabs and will be reflectedwithin the destination database file.

Tasks which can be performed on the Relationships tab include:[1] importing Relationships, TOs, Custom Functions and Value Lists from a DDR XML file,[2] manually adding one relationship at a time,[3] generating SQL code to represent a relationship in a SQL database (not used for TableConsolidation projects),[4] creating relationships within a SQL database (not used for Table Consolidation projects),[5] creating relationships within a FileMaker Advanced database,[6] deleting selected relationships,[7] changing Left Table name,[8] changing Left Table Cascade Create status,[9] changing Left Table Cascade Delete status,[10] changing Right Table name,[11] changing Right Table Cascade Create status,[12] changing Right Table Cascade Delete status,[13] manually changing relationship predicate parameters,[14] manually adding a relationship predicate,[15] manually deleting a selected relationship predicate.



39/97

Step 4 - Click Import Relationships Button

Click the Import Relationships button to import relationships from the DDR XML file for the sourcedatabase file.



40/97

Step 4 - Select DDR XML File

The relationships will be imported from the DDR file and added to the list of relationships on theRelationships tab. TOs, Value Lists and Custom Functions will also be imported from the DDR XML fileat the same time, and displayed under the Value Lists and CFs tabs. A dialog will be displayed if thereare no Custom Functions or Value Lists found within the DDR XML file.



41/97

Step 4 - Remap TOs

It imay be necessary to change TOs when performing a Table Consolidation project. Once theRelationships and TOs have been imported, the developer should analyze the usage of these importedobjects and review how they were used within the original separate FileMaker database files. For



42/97

instance, if there were a dozen source database files, and if multiple TOs were created to point to thesame base table, then these TOs should probably be renamed in the new consolidated database file.

FmPro Migrator lists the base table and source filenames within the list of TOs, in order to assist thedeveloper with this renaming process. During the Step 5 Remap Objects process, each of theserenamed TOs will be automatically renamed to the new values within each Relationship, Layout objectand ScriptMaker script.

This screenshot shows a TO named Client which will be renamed to Client_New2.



43/97

Step 4 - Value List - Details

Clicking on the Value Lists tab displays the Value Lists which were imported from the DDR XML file.Value Lists shown with a type of Custom, are static value lists having a manually edited list of values(as shown in this screenshot). Value Lists displayed with a type of Field, are dynamically generated



44/97

value lists which get their value from a field within the database.Static value list items can be manually edited by clicking on the Value List and changing the values.Changes are saved automatically when clicking out of the Static Value List field.



45/97

Step 4 - Custom Function - Details

Clicking on the CFs tab displays the Custom Functions which were imported from the DDR XML file.Custom Functions and their parameter lists are displayed.The Custom Function Code can be manually edited by clicking on the Custom Function and changing



46/97

contents of the Custom Function Code field. Changes are saved automatically when clicking out of theCustom Function Code field.



47/97

Step 5



48/97

Step 5 - Remap Objects

Step 5 - Remap Objects

Click the Step 5 - Remap Objects button to remap changed TOs within all Relationships, Layout objects



49/97

and Scripts. Layout text Search & Replace tasks will also be performed.

External filename dependencies are removed from within each Script because all of the Scripts will nowrun from the new destination file where all of the tables are being consolidated.

Note: The FileMakerDB.fp7 file should not be open within FileMaker Advanced when clicking thisbutton, as FmPro Migrator will be attempting to open this file automatically at the end of the Step 5Script processing.



50/97

Step 6



51/97

Step 6 - Create Tables, TOs and Relationships

Step 6 - Create Tables, TOs and Relationships

Close any source database files which might still be open from previous steps.



52/97

If necessary, open the FileMakerDB.fp7 file within the output directory using FileMaker Advanced. Thisfile was created and should have been opened automatically by FmPro Migrator during Step 5.

This file has been customized for Table Consolidation projects with the addition of scripts/layouts and aplaceholder TO required during the migration process.

If you want to use your own existing file as the destination file, then copy these objects into yourdatabase file:1) Copy the table named "= Placeholder TO".2) Copy the ScriptMaker scripts [used on Windows only].3) Copy the "Get TOs List" layout [used on Windows only].4) Make sure that there aren't any TOs within your database file starting with the "=" character. Thisplaceholder TO is used by the QuicKeys/WinAutomation scripts while creating Relationships, in order tomake sure that the correct TO is being selected from TO menu lists. Each time a TO is selected from aTO list, the "=" character is sent to initialize FileMaker to this specific placeholder TO in the list beforesending the characters of the TO name.5) Make sure that the Save Layout Changes Automatically option is checked on the Layouts tab ofFileMaker preferences for the file. The automated scripts which create the layouts are not designed toclick on the Ok dialog to save layout changes for each layout as it is being created.



53/97

Step 6 - Create Tables - Copy Tables to ClipBoard

Click the Copy All Tables to ClipBoard button on the Tables tab.

All of the source tables will be put onto the ClipBoard, ready for pasting into FileMaker Advanced.



54/97

Step 6 - Create Tables - Paste Tables From ClipBoard

Select Define/Manage Database from the File menu within FileMaker Advanced.

Click the Paste button.

Note: If the Paste button is grayed out, this means that the table XML code didn't get copied to theClipBoard before the Define/Manage Database dialog was opened. If this happens, click the Copy AllTables to ClipBoard button again from within FmPro Migrator.



55/97

Step 6 - Create Tables - Paste Tables From ClipBoard

The tables will be pasted from the ClipBoard, and displayed in the Define/Manage Database window.



56/97

Step 6 - Create TOs

Click the TOs tab.

Click the Create All TOs in FileMaker button, to build the non-Base Table TOs within the destination



57/97

FileMaker database file.

Step 6 - Create TOs - [Mac OS X Dialog]

Click the Ok button on the Create TOs dialog, since QuicKeys and the required shortcuts have alreadybeen installed.

Step 6 - Create TOs - [Mac OS X Status Area]

The RelationshipGraph window will be opened within FileMaker, and each of the TOs will be created.

It is not generally necessary for you to click any of these buttons in the status area. These buttonsperform the following tasks:Next TO - This button gets clicked by the QuicKeys shortcut after it creates each TO, in order to startthe process of creating the next TO.Current TO - If the QuicKeys shortcut gets stuck in some way and fails to create a TO, you can click onthis button to attempt re-creating the TO currently being processed.Done - Click this button if you want to cancel the TO creation process.



58/97

Step 6 - Create TOs - [Windows Dialog]

Click the Ok button on the Create TOs dialog, since WinAutomation and the required jobs have alreadybeen installed.

Step 6 - Create TOs - [Windows Status Area]

The RelationshipGraph window will be opened within FileMaker, and each of the TOs will be created.

It is not generally necessary for you to click any of these buttons in the status area. These buttonsperform the following tasks:Next TO - This button gets clicked by the WinAutomation job after it creates each TO, in order to startthe process of creating the next TO.Current TO - If the WinAutomation job gets stuck in some way and fails to create a TO, you can click on

this button to attempt re-creating the TO currently being processed.Done - Click this button if you want to cancel the TO creation process.



59/97

Step 6 - Create Relationships

Click the Relationships tab.

Click the Create All Relationships in FileMaker button.



60/97

Step 6 - Create Relationships - [Mac OS X Dialog]

Click the Ok button on the Create Relationships dialog, since QuicKeys and the required shortcuts havealready been installed.

Step 6 - Create Relationships - [ Mac OS X Status Area]

The Relationships window will be opened within FileMaker, and each of the Relationships will becreated.

It is not generally necessary for you to click any of the buttons in the status area. These buttonsperform the following tasks:

Next Relationship - This button gets clicked by the QuicKeys shortcut after it creates each Relationship,in order to start the process of creating the next Relationship.

Current Relationship - If the QuicKeys shortcut gets stuck in some way and fails to create aRelationship, you can click on this button to attempt re-creating the Relationship currently beingprocessed.



61/97

Done - Click this button if you want to cancel the Relationship creation process.

Step 6 - Create Relationships - [Windows Dialog #1]

Click the Ok button on the Create Relationships dialog, since WinAutomation and the required jobshave already been installed.


FmPro Migrator needs to gather a list of Table Occurrences from the destination database sorted inalphabetical order using FileMaker's sorting algorithm. This list of TOs will be used when selecting TOsfrom menus when creating each Relationship.

Switch to the FileMaker database, don't click on the Ok button yet.



62/97

Step 6 - Create Relationships - Get TOs List [Windows]

Click the Get TOs List button on the Get TOs List layout in the destination database.



63/97


Once the TOs list has been gathered from the destination database, click the Ok button displayed byFileMaker.


Now that the alphabetical list of TOs are on the ClipBoard, click the Ok button so that FmPro Migratorcan retrieve them from the ClipBoard.

Step 6 - Create Relationships - [ Windows Status Area]

It is not generally necessary for you to click any of the buttons in the status area. These buttons



64/97

perform the following tasks:

Next Relationship - This button gets clicked by the WinAutomation job after it creates eachRelationship, in order to start the process of creating the next Relationship.

Current Relationship - If the WinAutomation job gets stuck in some way and fails to create aRelationship, you can click on this button to attempt re-creating the Relationship currently beingprocessed.

Done - Click this button if you want to cancel the Relationship creation process.

Step 6 - Review Created TOs and Relationships

After creating all of the TOs and Relationships, it is recommended that the new Relationships and TOsbe reviewed on the RelationshipGraph window. When reviewing the relationships, consider whetherany new TOs were created. When the FileMaker Pro Advanced database creates Relationships, extraTOs are created in situations which would result in more than 1 set of links to a single TO.

When converting a multi-file solution into a single file solution, check to see if are any existingrelationships which will be duplicated within the new consolidated database file. Having the same

relationship duplicated multiple times, will result in addition TOs created having the same name as theoriginal TO, but also having an incrementing number appended to the TO. These additionalrelationships can be made to work in the new file, but would likely require manually pointing fields andportals on Layouts to a different TO on the RelationshipGraph - thus requiring extra unnecessary workat the end of the conversion process.Therefore duplicated or unused relationships should be deleted from the Relationships tab withinFmPro Migrator. At this point in the process, the unneeded relationships could be deleted from theRelationships tab within FmPro Migrator and then all of the relationships could be re-created using theStep 6 instructions.

Note: It will be necessary to manually delete any relationships or non-base table TOs which wereautomatically created on the RelationshipGraph within FileMaker Pro Advanced. If there are manyitems which need to be deleted, it may be easier to delete all objects on the RelationshipGraph, thendelete and re-paste the Table XML definitions via the ClipBoard.

Deleting of TOs within FmPro Migrator is not recommended, because they should simply be remappedto the correct TO in the new consolidated file. If this type of change is required at this point in the



65/97

process, press the Step 5 button again to remap TOs after making any changes to the New TO Namefields.



66/97

Step 6 - Create Custom Functions


Click the Step 6 button to start the process of creating Custom Functions in the new consolidated



67/97

database file. Custom Functions should be created before pasting the tables into the new consolidateddatabase file in case the Custom Functions are used within the definition of Calculation field definitions.Skip this step if there are no Custom Functions within your database files.


Click the Ok button on the information dialog.Click the CFs folder tab.



68/97


Click the Create All Custom Functions button.



69/97

Step 6 - Create Custom Functions - [Mac OS X Dialog]

Click the Ok button on the Create Custom Functions dialog, since QuicKeys and the required shortcutshave already been installed.

Step 6 - Create Custom Functions - [Mac OS X Status Area]

The Define/Manage Custom Functions window will be opened within FileMaker, and each of theCustom Functions will be created.

It is generally not necessary to click any of the buttons in the status area. These buttons perform thefollowing tasks:

Next CF - This button gets clicked by the QuicKeys shortcut after it creates each Custom Function, inorder to start the process of creating the next Custom Function.Current CF - If the QuicKeys shortcut gets stuck in some way and fails to create a Custom Function,this button can be clicked in order to attempt re-creating the Custom Function currently beingprocessed.Done - Click this button if you want to cancel the Custom Function creation process.



70/97

Step 6 - Create Custom Functions - [Windows Dialog]

Click the Ok button on the Create Custom Functions dialog, since WinAutomation and the required jobshave already been installed.

Step 6 - Create Custom Functions - [Windows Status Area]

The Define/Manage Custom Functions window will be opened within FileMaker, and each of theCustom Functions will be created.

It is generally not necessary to click any of the buttons in the status area. These buttons perform thefollowing tasks:Next CF - This button gets clicked by the WinAutomation job after it creates each Custom Function, inorder to start the process of creating the next Custom Function.Current CF - If the WinAutomation job gets stuck in some way and fails to create a Custom Function,

this button can be clicked in order to attempt re-creating the Custom Function currently beingprocessed.Done - Click this button if you want to cancel the Custom Function creation process.



71/97

Step 7



72/97

Step 7 - Create Scripts and Layouts

Step 7 - Create Scripts and Layouts

Click on the Layouts tab.



73/97

Scripts and Layouts are processed in the following manner:1) Copy all of the Layouts from FmPro Migrator into the destination FileMaker database, with thePass#1 pop-up menu selected.2) Copy the Scripts from FmPro Migrator and paste into the ScriptMaker window within the destinationFileMaker database.3) Re-create each of the layouts again within the FileMaker destination database, with the Pass#2pop-up menu selected. This 2nd pass resolves issues with circular dependencies between Layouts andScripts.



74/97

Step 7 - Create Layouts - Pass#1

On the Layouts tab, click the Create All Layouts in FileMaker button. The Pass#1 pop-up menu shouldbe selected under the Create All Layouts in FileMaker button.



75/97

Step 7 - Create Layouts - [Mac OS X Dialog]

Click the Ok button on the Create Layouts dialog, since QuicKeys and the required shortcuts havealready been installed.

Step 7 - Create Layouts - [ Mac OS X Status Area]

The data window will be opened in Layout mode within FileMaker, and each of the Layouts will becreated from the information stored within FmPro Migrator.


Next Layout - This button gets clicked by the QuicKeys shortcut after it creates each Layout, in order tostart the process of creating the next Layout.

Current Layout - If the QuicKeys shortcut gets stuck in some way and fails to create a Layout, you canclick on this button to attempt re-creating the Layout currently being processed.



76/97


77/97

Step 7 - Create Layouts - Get TOs List [Windows]

Click the Get TOs List button on the Get TOs List layout in the destination database.



78/97


79/97

Step 7 - Create Layouts - [Windows Dialog #3]

Once the TOs list has been gathered from the destination database, click the Ok button displayed byFileMaker.

Step 7 - Create Layouts - [ Windows Status Area]


Next Layout - This button gets clicked by the WinAutomation job after it creates each Layout, in order tostart the process of creating the next Layout.

Current Layout - If the WinAutomation job gets stuck in some way and fails to create a Layout, you canclick on this button to attempt re-creating the Layout currently being processed.

Done - Click this button if you want to cancel the Layout creation process.



80/97

Step 7 - Create Scripts - Copy Scripts From FmPro Migrator to ClipBoard

Click the Copy All Scripts to ClipBoard button.



81/97

Step 7 - Create Scripts - Paste Scripts From ClipBoard into FileMaker

Open the ScriptMaker window, select Paste from the Edit menu.

All of the consolidated and remapped scripts from FmPro Migrator will be pasted into the destination

FileMaker database.

At this point in the process, there are no more unresolved dependencies between scripts and layoutsbecause the layouts have all been created. But there are unresolved dependencies between layoutobjects and scripts, which will be resolved when the layouts are recreated in Pass#2.



82/97

Step 7 - Create Layouts - Select Pass#2 Menu

Selecting the Pass#2 menu instructs FmPro Migrator to replace the contents of existing layouts insteadof creating new layouts within the FileMaker database.



83/97

Step 7 - Create Layouts - Pass#2

Each of the layouts has already been created within the FileMaker database. During the 2nd Pass, thecontents of each layout will be deleted and replaced, but the actual layout itself will not be deleted. Thisprocess resolves dependencies between layouts and scripts without adversely affecting the



84/97

dependencies between scripts and layouts.

Note: It is important to not add, remove or rearrange layouts between the Pass#1 and Pass#2processing. FmPro Migrator is expecting a there to be exactly 1 more layout than the number of layoutslisted in the layouts field, and is expecting each of the layouts to be displayed in the same order as theyare listed (alphabetically) within the layouts list field. FmPro Migrator will automatically skip past the firstlayout named "Get TOs List" and start replacing layout contents with the 2nd layout in the database.



85/97

Step 7 - Create Value Lists


Click the Step 7 button to start the process of creating Value Lists in the new consolidated database



86/97

file. Value Lists should be created before creating Layouts within the new consolidated database file inorder to resolve dependencies between Layout objects and Value Lists which need to exist beforecreating the Layout objects.Skip this step if there are no Value Lists within your database files.


Click the Ok button on the information dialog.After the Ok button has been clicked, the Value Lists screen will be displayed.



87/97

Step 7 - Create Value Lists - Click Create All Value Lists Button

Click the Create All Value Lists button.



88/97

Step 6 - Create Value Lists - [Mac OS X Dialog]

Click the Ok button on the Create Value Lists dialog, since QuicKeys and the required shortcuts havealready been installed.

Step 6 - Create Value Lists - [Mac OS X Status Area]

The Define/Manage Value Lists window will be opened within FileMaker Pro Advanced, and each of theValue Lists will be created.

It is generally not necessary to click any of the buttons in the status area. These buttons perform the

following tasks:Next VL - This button gets clicked by the QuicKeys shortcut after it creates each Value List, in order tostart the process of creating the next Value List.Current VL - If the QuicKeys shortcut gets stuck in some way and fails to create a Value List, this buttoncan be clicked in order to attempt re-creating the Value List currently being processed.Done - Click this button if you want to cancel the Value List creation process.



89/97

Step 6 - Create Value Lists - [Windows Dialog]

Click the Ok button on the Create Value Lists dialog, since WinAutomation and the required jobs havealready been installed.

Step 6 - Create Value Lists - [Windows Status Area]

The Define/Manage Value Lists window will be opened within FileMaker Pro Advanced, and each of theValue Lists will be created.

It is generally not necessary to click any of the buttons in the status area. These buttons perform thefollowing tasks:Next VL - This button gets clicked by the WinAutomation job after it creates each Value List, in order tostart the process of creating the next Value List.

Current VL - If the WinAutomation job gets stuck in some way and fails to create a Value List, thisbutton can be clicked in order to attempt re-creating the Value List currently being processed.Done - Click this button if you want to cancel the Value List creation process.



90/97

Step 8



91/97

Step 8 - Create Import Scripts

Step 8 - Create Import Scripts

At this point in the Table Consolidation process, all of the database objects have been created within



92/97


93/97

Step 8 - Paste Scripts into FileMaker

Open the FileMaker ScriptMaker window, and select Paste from the Edit menu.

If the Paste option is not available for selecting, close and re-open the ScriptMaker window.

Step 8 - Using the Import Scripts

The import scripts are created using the following design criteria:

1) Each source file contains only one table and the filename is Tablename.fp7 .2) Each base table has a corresponding layout in the destination database having a Layout name



94/97

exactly the same as the base table name.Note: This is not always the case with migrated files. It will generally be necessary to select anappropriate layout to use for the Goto Layout statement at the start of each import script.3) Each of the source files are located within the same folder as the destination file.Since modifications may be required to the import scripts, it is recommended that they be run one at atime the first time they are run, for testing purposes. Executing the _Import All Tables script willconveniently run all of the scripts and import data into all of the tables.



95/97

Finishing Up



96/97

Manual Completion Tasks

Manual Completion TasksSome tasks can't be completed automatically within a FileMaker database, and require manualintervention.

1) Objects on the RelationshipGraph can't be moved automatically to create an easy to read display. Itis often helpful to move and colorize TOs according to how they are being used within a solution. Thistask can only be done manually. However if you previously colorized the TOs in the original sourcefiles, FmPro Migrator does retain these colors during the TO creation process.

2) Layout Header, Body, Footer locations cannot be automatically specified during Layout creation. Thepositions of these Layout parts are not stored within the DDR XML file or the Layout XML code placedonto the ClipBoard. Therefore these Layout parts need to be moved into position manually.When FmPro Migrator creates each layout during Pass#1 processing, the Header and Footer layoutparts are automatically deleted from the layout. This is done in order to make it easier for the developerto manually add the necessary layout parts. It is quicker to add a new layout part than it is to resize,move or delete existing layout parts which already contain layout objects.

3) Layout print settings need to manually set for each layout.

4) Dynamic value lists are created during Step 6 of the table consolidation process. These dynamicvalue list names are placeholders which require the developer to manually select the field displayoptions.

5) Review the Relationships and TOs which were created in Step 6 to verify whether the originallydefined TOs should be used within each Layout object, portal and script. New TOs may have beencreated by FileMaker Pro Advanced during the automated relationship creation process. New TOscould have been created unnecessarily if there were duplicate copies of relationships imported fromeach individual file. It will typically be quicker to delete these duplicate relationships and re-do Steps 6,7 and 8 using a new empty file rather than try to repoint each field, portal and script step to the correctTO.Note: To get FmPro Migrator to create a new empty FileMakerDB.fp7 file, close and rename theexisting file, click the Step 5 button to Remap Objects and a new empty FileMakerDB.fp7 file will becreated within the output directory.



97/97

6) Testing. Each Script, button and Layout should be tested to verify correct operation. Since the testingprocess could take some time, it can be useful to use the _Import All Tables script to reimport the datafrom the live solution once development and testing has been completed. To make an empty file forre-importing purposes, you can simply select Save A Copy As... [clone - no records] from the File menu.

FmPro Migrator Developer Edition Table Consolidation Procedure

Documents

Transcript of FmPro Migrator Developer Edition Table Consolidation Procedure