Bug with FileMaker Pro 12.0v2 (OS X) and externally stored containers?

Discussion created by ChadNovotny on Jul 12, 2012
Latest reply on Jul 13, 2012 by Stephen Huston

I posted this also at Can anyone confirm this bug? Have not yet tested on Windows or Snow Leopard.


Files added to an externally stored container appear as still in use by FileMaker process

Product: FileMaker Pro

Version: 12.0v2

Operating system version: OS X 10.7.4

Description of the issue: When adding a file to a container stored externally (NOT as a reference), the file continues to be reported as in use by the FileMaker process. As it appears to be in use, it cannot be overwritten or deleted. This impacts scripts that save as PDF to a temp path, insert the new PDF into a container, and then attempt to modify the existing PDF (such as append).


Steps to reproduce the problem:

1. Create a file with a single container field (using standard storage) and one record.

2. Save as PDF to the desktop, naming as "Untitled.PDF"

3. Insert the new file into the container field (DO NOT use "store as reference")

4. Try Save as PDF again, overwriting the existing "Untitled.PDF" file (this should work)

5. In field options, change the storage of the container field to secure external storage

6. Clear the container field again, and re-add the Untitled.PDF file to the container (again, NOT as a reference)

7. Try Save as PDF again, overwriting the existing file on the desktop


Expected result:As with the first test (when the container used standard storage), the Save as PDF should succeed and overwrite the file on the desktop


Actual result:You receive an error telling you to use a different name or path. Using the Terminal command

lsof | greg Untitled.PDF

shows that the file is in use by FileMaker.


This did not appear to be happening in FileMaker 12.0v1

Adding another file to the field on a different record "releases" the original file that appears in use.