While versions 12-16 all work with the same file format, new features in later versions are not backward compatible and will not be available to users of earlier versions. Features CompatibilityĮach new version of FileMaker comes with new client-facing features available for implementation. There are, however, a few compatibility issues to be aware of. Users simply upgrade their client to FileMaker Pro 16, and for hosted databases, the server is upgraded to FileMaker Server 16.

fmp12 file format as v12-15, so upgrading to the latest version does not require a file conversion of the database file(s) themselves. Upgrading from versions 12-15įileMaker 16 uses the same. Inactive files required for archival purposes should be converted to the current version of FileMaker and backed up or archived, and earlier versions of those files sitting on your computer should be removed from your local machine. Please review MIT's policies about storage of data on the Security Team's InfoProtect web pages. If you are thinking of upgrading to the latest version of FileMaker, now is also good opportunity to take inventory of all of your FileMaker files to determine if they are properly secured and to make sure that they are not being used to store PIRN data. See below for more information on file conversion. fmp12 format in order to be opened by FileMaker 16. fp7 file format or earlier, used by versions 11 and earlier, must be converted to the. See Upgrading from versions 12-15 below for more information.ĭatabases with the. However, there are some compatibility issues between v16 and v12-15 to keep in mind. fmp12 file format, used by versions 12 and up, may be opened by FileMaker Pro 16 and hosted by FileMaker Server 16, with no file conversion necessary.

FileMaker 16 is the current recommended version of the FileMaker platform at MIT, and we encourage anyone running FileMaker Pro and (if applicable) FileMaker Server to upgrade to the latest version.įileMaker databases with the.

Filemaker pro 16 user guide