FileMaker Pro to Revolution Conversion Procedure
Convert FileMaker Pro® Layouts and ScriptMakerTM scripts with FmPro Migrator Developer Edition

by David Simpson

This tutorial series explains the process of converting FileMaker Pro® Layouts and ScriptMakerTM scripts into Revolution stacks with FmPro Migrator Developer Edition. FmPro Migrator Developer Edition converts each FileMaker layout into a Revolution card, containing all of the fields, portals, text, images and buttons from the original layout. The generated stack file provides a foundation for further development of a full featured database application utilizing the Revolution IDE. Revolution compiled stand-alone apps support a wide variety of database servers including FileMaker Server Advanced (ODBC), SQLite and Valentina (for embedded applications), and networked SQL databases including: MySQL, Oracle, SQL Server, PostgreSQL and any other ODBC compatible database server.

Additionally, this tutorial will provide information about the FmPro custom property set included in each card of the generated stack file.

In this article we will look at what the converter does and how to gather the initial information from your Filemaker Pro application.

Original FileMaker Pro Layout

FmPro Migrator Developer Edition reads the XML definition of a FileMaker layout, and then converts this information into a Revolution card containing all of the fields, portals, text, images and buttons from the original layout. An original layout for the sample Asset Management database is shown in the previous image.

Converted Revolution Card

The resulting Revolution card is shown in this screenshot. Each field is filled with the name of the original Tablename::Fieldname information from the original FileMaker Pro Layout. A Status Area background object is provided at the left hand side of the card, to simulate the Browse/Find modes from the original database. Menus and scripts are provided in the template stack file for hiding/showing the status area and moving the card objects to accommodate the Status Area. Each original layout name is used as the name for the Revolution card, and when the Layout drop down menu is selected, a "go to card" instruction is executed, taking the user to the selected card.

The card objects are placed into a Geometry Manager enabled group named "Layout_Objects_Group". As the card is resized, the Layout_Objects_Group is also resized. If the window is too small to show all of the objects, scrollbars automatically appear to enable scrolling by the user.

Converted ScriptMaker Script Code

If ScriptMaker scripts have been copied into FmPro Migrator Developer Edition via the ClipBoard, then these scripts will be converted into Revolution handlers. The 34 most commonly used (out of 140) ScriptMaker steps are converted directly into Revolution code. ScriptMaker commands such as Go to Layout are converted into Revolution's "go to card" command, the Freeze Window/Refresh Window commands are converted into "lock screen/unlock screen" commands. ScriptMaker commands which fill variables and fields are converted into the Revolution "put" command.

All of these converted scripts will require additional development after the conversion process has been completed by FmPro Migrator Developer Edition, as these conversions are primarily intended to reduce the amount of typing required by the Revolution developer.Gathering Info from FileMaker Pro

Step 1 - Perform Table/Data Migration

Use the instructions on the www.fmpromigrator.com Support web pages for the type of migration you want to perform. This process involves gathering metadata from the FileMaker database, creating the tables in the destination database and transferring data into the destination database.

Step 2 - Copy Layouts Individually

Click the Add Layout from Clipboard button, to import layouts one at a time from FileMaker Pro into FmPro Migrator Developer Edition.

Select all of the objects on a Layout, then copy the layout onto the Clipboard within FileMaker Pro. Once the Layout has been copied, click the Add Layout from Clipboard button on the Layout tab within FmPro Migrator Developer Edition.

Once the Layout has been added to the list, give the Layout a name, matching its name in the original FileMaker Pro database. This individual layout capture process is best suited for importing small numbers of layouts from the original FileMaker Pro database.

Note: Layout and ScriptMaker names should not include Unicode characters, as these names will become the names of cards and handlers within the Revolution stack.

Step 3 - Copy Layouts in Batch Mode

Click the Import All Layouts button to import all of the layouts from the currently open FileMaker Pro database file. This batch capture process utilizes QuicKeys/WinAutomation shortcuts to control the FileMaker Pro database while capturing the layouts into FmPro Migrator Developer Edition. This process involves the installation and setup of either QuicKeys or WinAutomation software on your computer (depending upon operating system in use), and the use of FileMaker Pro Advanced to create a DDR XML file.

When this automated procedure is used, each layout will be imported into FmPro Migrator Developer Edition and the layout will automatically be given the correct name as it was read from the DDR XML file exported by FileMaker Pro Advanced.

Our next article will cover converting to Revolution in detail.