FmPro Migrator 6.85
mPro Migrator quickly and accurately migrates FileMaker Pro database structure and data to MySQL, Oracle, Access, SQL Server, Sybase, DB2, OpenBase, PostgreSQL, FrontBase, SQLite and Valentina.
-- Converts FileMaker layouts into PHP web applications [Platinum Edition]
-- Converts Access Forms/Reports, Relationships, Value Lists, Queries and Visual Basic to FileMaker 11 [Platinum Edition]
-- Converts Visual FoxPro projects into any supported database or IDE [Platinum Edition]
-- Converts FileMaker Pro, Access, Visual FoxPro projects into Visual Studio 2010 .Net 4 [Platinum Edition]
-- Converts FileMaker Pro Layouts/Scripts/Value Lists to Microsoft Access [Platinum Edition]
-- Converts FileMaker Pro Layouts/Scripts/Value Lists, Relationships to Servoy Projects [Platinum Edition]
-- Converts Layouts to HTML/JavaScript
-- Migrates Access, Firebird and SQL Server to FileMaker 11
-- Automated Table Consolidation Feature
-- Facilitates FileMaker ESS Configurations
-- Host FileMaker Pro data at any ISP supporting MySQL
-- Migration of large text fields and image data for all supported databases
-- No ODBC driver licensing required for UNIX servers
-- Repeating Fields Extraction
-- Economical Single-User License
-- FileMaker image export feature
-- Export Layout XML to individual files
-- PHP to LiveCode Conversion (Platinum Edition Feature)
-- BASIC to LiveCode Conversion (Platinum Edition Feature)
-- Database to LiveCode Conversion (Platinum Edition Feature)
FileMaker Pro database fields containing more than 255 or 4000 characters of text are migrated to the appropriate large text column type in the destination database. Container field data within FileMaker Pro container fields is migrated directly to the appropriate BLOB type of database columns through a network connection. No manual data entry is required for processing either of these specialized data types.
FmPro Migrator is available for MacOS X and Windows.
Requirements
Changes: 6.85
2) Added conversion of FileMaker Stored and Unstored Calculation fields into PHP code. The Unstored Calculation fields are implemented within the view and edit actions of any form controller for which the field is displayed on the form. Since Unstored Calculation values are written into the model when calculated, the values are effectively stored as well. Stored Calculations are calculated within the model whenever a record is saved.
3) Added conversion of WebViewer layout objects, including support for parsing WebViewer URLs with field name substitution within the generated PHP code. This feature also directly supports WebViewer objects being used with the 360Works SuperContainer product.
