In order to convert a database from FileMaker to PostgreSQL, the most common method will be to manually create each table, and make decisions about field type definitions. 'Field Definition' components and the FileMaker data however, can be converted to PostgreSQL tables fairly easily. To facilitate this process, diagramming your basic metaphors and the way users interact with your system is very useful.

Since PostgreSQL has a variety of front-ends available to provide the user interface (pg_access, web-based interfaces using perl, ColdFusion and other web programming languages), the user interface must also be re-written from the ground up. 'User Interface' and 'Script' components are specific to FileMaker, having no equivalents in either SQL or in PostgreSQL, and are thus, sadly, not possible to port to PostgreSQL without complete ground up re-writes.

Scripts written in FileMaker for added functionality.

The data definitions on individual fields you create. available allowing you to enter, display and manipulate data, as well as change the format of reporting of data. These are the text boxes, buttons, menus, layouts, etc. If working with a multi-table Filemaker Pro file, the same basic process can be followed: create tables in PostgreSQL to match the tables in Filemaker Pro, then export and import the data.įileMaker Pro databases, in a generalized description, have 4 basic

Take each file one at a time, and recreate them as PostgreSQL tables.įor versions of Filemaker Pro 7 and later:Īll tables can be contained in a single Filemaker Pro file, or they can be in individual files (which will commonly be the case with databases converted from version 6). So when converting from FileMaker to PostgreSQL, Often, what is considered a single database is several or many Is a relational DBMS, but the relationships are between different files inįileMaker Pro. The DBMS is not as standards-compliant as other are.įor versions of Filemaker Pro 6 and earlier:įileMaker files are the equivalent of individual PostgreSQL tables. ODBC and SQL have come relatively late to FileMaker, thus In general, it is more user friendly than FileMaker Pro is now the only regularly used cross-platform With Apple (like ClarisWorks, which became AppleWorks) and FileMaker became Around 1998, Claris split, some components going 3 Data export from FileMaker and import into PostgreSQLįileMaker Pro is a database originally developed on the Macintosh by Claris, a.

How to make a filemaker pro database