Upgrade filemaker pro 6
Version 16 introduced few major end user changes of note, but if you are developing in FileMaker 16, it is best to make sure all the users of your system have updated to 16 as well. For example, v12 users will not see slide controls or popovers which were introduced in v13. In most cases, such features would simply be invisible to clients running earlier versions. 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.
#Upgrade filemaker pro 6 upgrade#
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. If you would like assistance in this process, we can complete this task for you at a minimal cost.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. PLEASE use MetaData Magic before converting your solution. It will also provide you with key information in the form of an error report that identifies what will likely need to be fixed once you convert. The “File Reference Fixer” removes unused file references that can cause issues in the converted files. that could be completely avoiding by employing this utility. NOT performing this step can leave you with A LOT of extra work later cleaning up old database references, etc. (We have no connection to New Millennium Data other than using their product successfully in many conversion projects.) fp5 FileMaker database BEFORE you do the file conversions. One absolute key to conversion is running an application called MetaData Magic on your original. Run MetaDataMagic on the original database files.Ģ.
This is a minimum of a three step process.ġ. That said, many people will want to at least try a straight conversion. Many companies invest in creating an entirely new database and only move the data from the old database into the new solution. Taking advantage on these new features such as multiple tables in one file, new security, and fully relational capabilities is called database migration and can be a much more costly proposition. Straight conversion of the files may be relatively simple, but it doesn’t guarantee the database will retain all the functionality it originally had…and it certainly won’t be optimized for using any of the new features available. So, if you have an old format database what do you do?
#Upgrade filemaker pro 6 mac os#
Modern versions of Mac OS (after 10.6 Snow Leopard), no longer support running FileMaker 6 or earlier…and so this is forcing these databases to be brought into the newer file formats just to be operational. fmp12 and we expect that format will last for many more years to come. The current FileMaker database file format is. Version 7 was good until the release of FileMaker 12 in 2012. In 2004, FileMaker completely rewrote FileMaker with version 7 and changed the file format to. fp5 (Version 5 of FileMaker) but this file format lasted through FileMaker version 6. We’re finding that there are still several organizations using FileMaker databases that were created many years ago with the old version of FileMaker. See our latest updated process for migrating your FileMaker database to the latest version of Claris FileMaker here.