FileMaker Pro 13.0v9 and up users cannot access access FileMaker Server 13.0v5 and earlier if the server has SSL encryption enabled but does not have a custom SSL certificate installed.Some examples of issues with mismatched server and client versions: In general, it's best practice to ensure FileMaker Server and all FileMaker Pro users accessing that server are all running on the same version of the platform.
If your database(s) are hosted, there are potential security-related compatibility issues when the version of FileMaker Server doesn't match the version of FileMaker Pro used to open a database. You also may want to enable the setting that specifies the minimum version of FileMaker Pro allowed to open your database file this will prevent users running earlier versions from logging in and seeing unexpected results.
Version 15 introduced few major end user changes of note, but if you are developing in FileMaker 15, it is best to make sure all the users of your system have updated to 15 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 using earlier versions. However, even though versions 12-15 all use 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 to developers. There are, however, a few compatibility issues to be aware of.
#FILEMAKER PRO MULTIPLE USERS UPGRADE#
Users simply need to upgrade to FileMaker Pro 15, and for hosted databases, the server is upgraded to FileMaker Server 15. fmp12 file format as v12-14, so upgrading to the latest version does not require a file conversion of the database file(s) themselves. Upgrading from versions 12-14įileMaker 15 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. fp3) also must be converted, but require special consideration. fmp12 format in order to be compatible with FileMaker 15. fp7 file format, used by versions 7-11, must be converted to. See "Upgrading from versions 12-14" below for more information.ĭatabases in the. However, there are some notable compatibility issues between v15 and v12-14. fmp12 file format, used by versions 12 and up, may be opened by FileMaker Pro 15 and hosted by FileMaker Server 15 with no file conversion necessary. FileMaker 15 is the current recommended version at MIT, and we encourage anyone running FileMaker Pro and (if applicable) FileMaker Server to upgrade to the latest version.įileMaker databases in the.
0 kommentar(er)
