Skip links

Beware of FileMaker 16 changes to existing solutions

filemaker-pro-16-advancedThe new version FileMaker 16 offers a lot of great new features. Overlay window in card design, copying of value lists, new functions, a REST API Interface and many other new possibilities.

Due to the many new features, developers and users of existing solutions should check whether all functions really work as desired before updating. This includes in particular checking whether all layouts are still displayed as before. In FileMaker 16, scrollbars have been removed so that windows are slightly smaller or may display more content. In the new version, the zoom control area has been removed - if you use this, you may need to integrate your own zoom control area. Some things are displayed differently on layouts with FileMaker 16 than with FileMaker 15.

Update to FileMaker 16.0.3 released

On October 9, 2017 FileMaker has released an update to version 16.0.3 for FileMaker Pro (Advanced), FileMaker Go and FileMaker Server has been released. In the new versions, among other things, the problem of destroyed databases during reconnect has been fixed. For this reason, it is strongly recommended that all FileMaker 16 users install the update to FileMaker 16.0.3 on all devices involved. Further information and download of the update can be found on the following pages:

FileMaker Pro: https://help.filemaker.com/app/answers/detail/a_id/16556
FileMaker Go:  https://help.filemaker.com/app/answers/detail/a_id/16558
FileMaker Server: https://help.filemaker.com/app/answers/detail/a_id/16557

FileMaker Pro 16 Client can destroy shared databases

Update on September 2, 2017: Under certain circumstances, a FileMaker Pro 16 client can destroy FileMaker databases that are shared on a FileMaker Server 15 or 16. This error has already been tested and confirmed by FileMaker. In the FileMaker Community there is a corresponding contribution to the problem.

This problem can occur if a Database is hidden (without a window), during which the connection is lost and a reconnect then takes place. The database may then contain deleted scripts and corrupt authorizations and cannot be restored.

  • Multi-file solution, one or more files opened "hidden", manual reconnect after disconnection: Error occurs.
  • Client uses Wi-Fi with Auto-Reconnect activated under the above conditions: Error occurs.
  • If the files were opened hidden, displayed and hidden again: Error does not occur.
  • If none of the hidden files contain scripts, the error does not occur.
  • If no reconnect is performed, the error does not occur.

Tip: If you are using FileMaker Pro 16 as a client on a FileMaker Server, we recommend, create backups more frequently and the Extend the historization of backups.

As a workaround, it is recommended that you do not open any databases hidden or with hidden windows. It should also be avoided to reconnect after a connection has been lost. However, this may not always be possible because FileMaker automatically attempts to reconnect when a connection is lost. There is also a topic for this problem in the German-language Forum of the FileMaker Magazine.

Update to FileMaker 16.0.2 released

On July 11, 2017 FileMaker has released an update to version 16.0.2 for FileMaker Pro (Advanced) and FileMaker Server. The following problems have been fixed in the new version:

  • After executing the "Go to object" script step on an empty Excerptwhich does not allow the creation of data sets, the focus was not set on the portal and the script step returned the error code 101 ("Data set missing").
  • If a data set was opened and closed again unchanged, the internal data set change number returned by the Get ( DatensatzÄnderungenAnzahl ) function increased.
  • The CryptAuthCode function returned incorrect results for encoded text entries.
  • The JSONGetElement function returned JSONBoolean and JSONNumber results as text instead of a number.
  • The functions JSONGetElement and JSONListValues returned the wrong decimal separator for comma-based locales.
  • External script steps did not correctly evaluate calculated values for repetitions.
  • The script step "Variable set" did not set large repeat values correctly.
  • The performance of the SortValues and UniqueValues functions has been improved.
  • Under certain circumstances, ESS-based tables displayed incorrect data records.
  • Windows: Dragging a PNG image between container fields did not work properly.
  • macOS: The Script-Debugger changed the scroll position when stepping through a script and showed the active script step at the bottom of the display area.

Windows user interface without a comprehensive window

One of the biggest innovations in FileMaker 16 is the user interface under Windows without an overarching window. This provides a significantly improved user experience, especially when using multiple screens, but can lead to problems with existing solutions.

FileMaker 16 on Windows

It is possible that some scripts may no longer work and need to be adapted for this situation. The menu bar should be active in at least one window, because if the menu bar is hidden in all windows, there is no way to use it.

Changes in FileMaker Core

FileMaker 16 contains some internal changes. WebViewer uses a new WebKit version on the Mac with a modified API. Christian Schmitz, developer of the MBS FileMaker plugin, reports that all plugin functions for the WebViewer no longer worked with FileMaker 16. Even though almost all functions are available again in the meantime, some important things are still missing - for example, there is still a problem with printing with the WKWebView-object. Some Cocoa programmers also face this problem. It is better not to switch to FileMaker 16 yet if you want your solution to print WebViewer content or output it as a PDF.

The fmp URL function now has a new privilege setting. If your solution uses fmp-URL functions, you must activate this permission so that this function is also available in FileMaker-16.

FileMaker 16 offers external script steps that can be defined in plugins. Even though this is a very interesting function, it is not yet integrated into the MBS FileMaker Plugin as the plugin would then no longer be backwards compatible and would no longer work with FileMaker 15 or older. The script step would be displayed as missing in older versions, and only a database design report would display the ID of the missing plugin.

Updated terms of use for FBA and VLA

If you are an FBA member (FileMaker Business Alliance) or participate in FileMaker's VLA (Volume Licensing Agreement) program, please note the changes to the terms of use. FBA members from the USA, for example, now require general liability insurance. The terms of use for the FileMaker Pro Advanced license included in the FBA program have also changed.

All in all, the upgrade to FileMaker 16 is a big step forward for FileMaker and offers a host of new features, includes hundreds of bug fixes and will certainly help the FileMaker community grow.

Translated with the kind permission of Monkeybread Software.

Caution when deleting portal data records

In a Tech document FileMaker informs you that the "Go to Object" function in FileMaker 16 works differently than in previous versions. When deleting portal records via script, this can lead to data loss under certain circumstances. If an empty Portalwhose relationship does not allow the creation of data records is the target of a "Go to object" script step, the script step returns the error code 101 ("Data record does not exist"). This change can lead to data loss under the following conditions:

A script to modify or delete portal rows does not include error handling to ensure that the portal is active

  • There are several portals on the current layout
  • The first portal in the creation sequence contains data records
  • Another portal on the current layout does not contain any data records
  • "Allow creation of data records via this relationship" is deactivated for the portal without data records

Example scenario

There are two portals on a layout, "Portal A" with data records and "Portal B" without data records. A button on the layout executes the following script:

Go to object [Name: "Portal B"]

Go to row of excerpts [Select entire content; First]

Delete portal row [without dialog box]

In FileMaker 15 and earlier, Go to Object does not return an error after selecting the empty portal B, and subsequent commands are not executed. In FileMaker 16, the [Go to Object] command returns error 101. FileMaker then executes the subsequent commands [Go to portal row] and [Delete portal row] in the next portal in which records are available. Without error handling in the script, this would lead to data loss in portal A (with records) because the first record in portal A would then be deleted. In this scenario, error handling must therefore be added:

Set error recording [On]

Go to object [Name: "Portal B"]

If [ Get(LastErrorNumber ≠ 0) ]

   Exit current script [ Get(LastErrorNumber) ]

Otherwise

   Go to clipping row [Select entire content; First]

   If [ Get(LastErrorNumber) = 0 AND Get(ActiveLayoutObjectName) = "Portal B" ]

      Delete portal row [without dialog box]

   End (If)

End (If)

In this example, an error handling function has been added that first checks whether an error has occurred. If so, the script is exited (portal empty). It then checks whether portal B is really active. If so, the record is deleted from the portal. FileMaker strongly recommends checking scripts for these constructs and adding error handling.

Customize Window feature in FileMaker Runtimes on Windows

In the FileMaker Magazine forum become knownthat the function "Customize window [Show all]" in FileMaker 16 Runtime-solutions on Windows can cause problems. Using this command in a FileMaker 16 runtime solution on Windows can cause reproducible crashes or prevent the runtime from starting with the error message "FileMaker Pro Runtime has stopped working". This problem only occurs in a runtime solution on Windows, but not in FileMaker Pro 16 on Windows.

Leave a comment

  1. Dear Mr. Markus Schall
    I am using FileMaker 11, and I have noticed when importing data records that the program
    is terminated unexpectedly and the error can be reported to Apple.
    My question: is my program version no longer compatible, do I have to buy a new version of FileMaker
    and which version is necessary for me, I am actually not a full professional, would a version 14 or 15 suffice?
    Thank you for your efforts
    Yours sincerely, Konrad Weber, Switzerland

    1. Hello Mr. Weber, the answer to your question will depend on which operating system you are using on your Mac. On the newer operating systems macOS 10.11 or 10.12, FileMaker 11 is no longer officially supported - but usually continues to run anyway. You could check whether it could also be due to your system configuration by creating a new user in macOS, starting the system with the new user and performing the import with the new user. If you decide to use a new FileMaker version, please note that a new file format (previously: fp7, from FM12: fmp12) is used from FileMaker 12 onwards. Your FileMaker solution must therefore first be converted to the newer fmp12 format with FileMaker 15 or 16, but this can usually be done without any problems. Best regards from FMK2017 in Salzburg!

      1. Thank you very much for your reply, my operating system is macOS High Sierra.
        My question: I would like a newer version of FileMaker 11 that I am using.
        Buy, at the moment I have a trial version FileMaker 16 and the purchase price is
        is actually too high for me I think a version 14 or 15 would help me
        and is slightly lower in price, and where can I buy them.
        Best regards Koni Weber

        1. Officially, only FileMaker Pro 16 can currently be purchased. I do not know whether and to what extent other dealers may still be selling older FileMaker versions. Sometimes older FileMaker versions are also sold on ebay or other marketplaces - however, it should be noted that in many cases such sales are made without a receipt.

  2. I have a similar problem. I have a FileMaker 11 version under High Sierra and have also used the files on the iPad with FM Go so far. After the last update on the iPad, the fp7 files could no longer be used. I then installed an FM 16 trial version and converted the files to fmp12 format to see how the new version works. However, after the FM 16 trial version has expired, my old fp7 files no longer work with my old FM 11 version. The program crashes. Strangely enough, this only affects the fmp7 files that I had previously converted to fmp12 format for testing purposes.
    What could be the reason for this?

Share this page:

ERP software as flexible as your company.
We will be happy to advise you.

Customizable ERP software for Mac, Windows and iOS.

You are here: Beware of FileMaker 16 changes to existing solutions