FmPro Migrator - The Universal Migration Tool for Visual FoxPro

FmPro Migrator Platinum Edition 6.46 - Adds Support for Servoy 6, and Includes PHP Conversion Enhancements.

Note: This feature is not currently compatible with the new FileMaker 12 file format.

Top 10 Features

Included with FmPro Migrator Platinum Edition, keeps your Visual FoxPro migration project affordable.
Quickly and economically test 6 different development environments - including for Apple iPhone/iPad.
Automated conversion of Visual FoxPro Forms/Reports to multiple development tools.
Copies .prg file and form FUNCTION/PROCEDURE code as commented code.
Data bound fields and grid controls are converted into equivalent SQL database data bound controls.
Persistent Visual FoxPro relations are converted into SQL database relationships (if needed).
Custom ComboBox lists are de-duped and centrally located as Value Lists.
Transfer data from locally stored DBF files into 11 SQL databases.
Converts pageframe form controls into Tab Controls including embedded objects.
Saves many hours of manual work converting each Form/Report.

For more info please send email or call.

Visual FoxPro Migration screenshot

Description

The Visual FoxPro Migration Service built into FmPro Migrator Platinum Edition provides an economical fixed-price migration or conversion service for Visual FoxPro projects. This service converts forms, reports, functions, procedures, persistent relations, and DBF data file conversion within a predefined budget. A wide range of target development environments are supported, including: Servoy, .NET 4 Visual Studio 2010, Microsoft Access, FileMaker Pro, FileMaker Go for iPhone/iPad, and LiveCode. All 6 conversion options are included for one fixed price.

Visual FoxPro Conversion Service Pricing
The Visual FoxPro Conversion Service License key is included with FmPro Migrator Platinum Edition.

FmPro Migrator Visual FoxPro Migration Options Diagram

Visual FoxPro to Multiple Development Environtments

The features and benefits of using the automated Visual FoxPro Migration Service include:

Multiple Conversion Options - Not sure which development environment you want to use? FmPro Migrator makes it possible for Visual FoxPro developers to quickly convert Visual FoxPro projects into 5 different development environments (including: Servoy, .NET 4 Visual Studio 2010, Microsoft Access, FileMaker Pro, FileMaker Go for iPhone/iPad, and LiveCode). All 5 conversion options are included for one fixed price.

Save Time, Get Up and Running Quickly - It can be a tedious and time consuming process to manually re-create each form/report object into any other development environment. Rather than spending days or even weeks of valuable time manually converting hundreds of forms/reports, Visual FoxPro developers can utilize the Visual FoxPro Migration Service as an economical alternative. FmPro Migrator Developer Edition typically processes each form/report within less than 1 second - much faster than you could perform the task manually!

The ability to efficiently perform Visual FoxPro migrations makes it possible to quickly show prototypes to prospective customers. An automated migration process represents the ultimate in rapid application development, which can't be matched by any other development environment. Being able to show customers a rapid prototype may make the difference in getting approval for a new client project.

Script Conversion - The Functions/Procedures within each .prg file and form are converted into commented individual scripts. These scripts are intended to be used as a template for the writing of new code within the new development environment.

The PHP Conversion feature can be used to convert Visual FoxPro applications into PHP web applications. Though the process generally works better using FileMaker Pro as the source database due to the guaranteed data binding information available from the original FileMaker Pro layout objects. It will generally be faster to data bind all FoxPro forms/fields prior to doing a conversion. Alternatively, the FoxPro application could be converted into a FileMaker Pro database, then the Layouts and fields could be data bound - then the FileMaker Pro database would be imported and converted using the PHP Conversion feature.

Visual FoxPro Static MetaData Export Process

FmPro Migrator uses a 2 step process to import the metadata from within Visual FoxPro projects. Thru the use of the included VFPExport.exe Utility, Visual FoxPro project metadata is read directly from the VCX, SCX, FRX, DBC, DBF, MNX and PRG files referenced within the .PJX project file. This information is written into a new database file named VFPExport.DBF.

VFPExport Static MetaData Import Process Diagram

Visual FoxPro Runtime MetaData Export Process

Since most Visual FoxPro projects contain VCX forms and objects having properties set only at runtime, an additional AppHook export process is also used to export project metadata. The VFPExport.exe utility is added to the startup code of the Visual FoxPro application. The Visual FoxPro developer compiles and runs their Visual FoxPro application as a user would use the application to open and close the forms within the application. One second after each form/report is instantiated, the ExportHook timer event fires and captures metadata for all of the objects on the current form/report. Once the Visual FoxPro application is closed, the new data is merged with the existing form/report data within the VFPExport.DBF file. By capturing this information during runtime, all inherited object properties will have been set by the application code, thus insuring that an accurate representation of the objects has been exported. The Visual FoxPro developer can easily modify the records within the VFPExport.DBF table in order to remove obsolete or unused form/report records.

VFPExport Runtime MetaData Export Processing

FmPro Migrator Visual FoxPro MetaData Import Processing

FmPro Migrator reads the contents of the VFPExport.DBF file and converts its contents into a standardized XML format which is stored within the FmPro Migrator MigrationProcess.db3 project database. Once the Visual FoxPro metadata has been converted into the standardized XML format, it can then be converted into any of the other database or development environments which are supported by FmPro Migrator.

FmPro Migrator Visual FoxPro MetaData Import Processing

Visual FoxPro Menu Conversion

The Visual FoxPro Menu Converter included with FmPro Migrator Developer Edition reads the GENMENU code from FoxPro .MPR files and converts the code into Servoy JavaScript code. Menus can be converted individually, as shown in the demo below, or can be converted for an entire Visual FoxPro project all at once. The Conversion Type menu provides two conversion options. Visual FoxPro menu STYLE parameters for menu items are converted into embedded HTML tags, supporting the style options: Bold, Italic, Underline, and Strikeout.

ON SELECTION statement procedure calls are converted into empty Servoy JavaScript functions to enable quick testing of the generated menu code.

Servoy App Menu JavaScript

A Servoy application menu can only be used within the SmartClient. Each menu appears under the last menu in the list of menu items. Menu items are displayed as submenu items.

Servoy Pop-Up Menu JavaScript

Servoy popup menus are typically attached to form objects, and are useable within SmartClient and WebClient deployed applications. The generated JavaScript code automatically displays the menu above/below the clicked object. PopUp menus can also be displayed at specific coordinate locations on the form canvas, by modifying the generated code.

Visual FoxPro Menu Converter - Online Demo
You can paste in your own FoxPro menu code into the revLet displayed below and instantly see the results.

Visual FoxPro Code Conversion

The Visual FoxPro Code Converter included with FmPro Migrator Developer Edition reads the contents of .PRG files and form code and converts the code into Servoy JavaScript code. Scripts can be converted individually, as shown in the demo below, or can be converted for an entire Visual FoxPro project all at once. Each line of code is analyzed and re-mapped (if possible) to equivalent JavaScript code which makes calls to Servoy API calls. Semicolons are added to each line and operators are remapped as necessary for JavaScript compatibility. Unsupported keywords are logged and displayed on the Statistics page of the application.