AnsweredAssumed Answered

FMP13, MacOS 10.9. Crash with data lost when change Container field from Picture to Interactive

Question asked by Norsult on Nov 19, 2014
Latest reply on Nov 20, 2014 by Benjamin Fehr

Summary

FMP13, MacOS 10.9. Crash with data lost when change Container field from Picture to Interactive

Product

FileMaker Pro

Version

13.0.3

Operating system version

MacOS 10.9.5

Description of the issue

Whenever you change the display style of a container field (Layout mode) from the default or preset value "optimzed for images" to "optimized for interactive" and then go back to browse mode, the application will crash.

If this happens with container fields set to remote storage in a secure way, i.e. encrypted, the data will be be lost since the re-opened, "recovered" file from the crash as described above, cannot accede the data any longer. The ValidateContainerdata() will also return FALSE.

(Verified on four different machines.
This does not occur with MacOS 10.7.5; tested on two machines)

Steps to reproduce the problem

The fastest and most reduced way to reproduce the issue is (in FM13.0.3 on MacOS 10.9.5):
New Database
in Field picker define a container field "MyContainer"
Drag "MyContainer" on Layout
switch to Browse mode
make New record (i.e. the first record)
click into  "MyContainer"
Insert picture 'temp.pdf'  (it does not matter if right-clicked or via menu, any PDF)
switch back to Layout mode
Duplicate layout object  "MyContainer"
Change the new object to 'optimised for interactive'
switch back Browse mode
create a new New record
again insert file temp.pdf (any PDF will do)
goto previous record

Expected result

After the steps the previous record should show, one displaying a static picture of the Pdf, the other, new occurrence of the field should show a pdf viewer like picture (depending on the chosen viewer like Preview, Adobe Reader etc.) and allow basic scrolling etc.

Actual result

When clicking into the interactive field at last, mostly with just loading the record for display, the application crashes.

Exact text of any error message(s) that appear

No FileMaker Error message - but the OS telling that the app FileMaker unexpectedly terminated...

Configuration information

Nothing else but OS 10.9.5 found to be minimum common denominator

Workaround

NONE

No pictures, but lot of crash reports pointing to an issue with interaction between FMP and the graphic lib of the OS

Outcomes