AnsweredAssumed Answered

Container data not stored in correct external path

Question asked by smcfeeters on Sep 25, 2012
Latest reply on Sep 26, 2012 by smcfeeters


Container data not stored in correct external path


FileMaker Server



Operating system version

OS X 10.8.2

Description of the issue

When a PDF is added to a container field, the original document is not stored in the defined external storage location, it is referenced directly from the location it loaded. 

When the document is dragged to the container field, it is stored in the correct location.  When the document is added to the container field via Applescript, it is not copied to the external data location, hence it is not found by other clients.

Steps to reproduce the problem

Create a database with a table containing a container field.
Create an applescript (based on folder actions) to copy new documents as they arrive in a folder into the database.
Add documents to the database, first dragging a PDF to the container field, then via the applescript.
Using Data Viewer example the container field.  Those documents added via Applescript are not stored in the container external storage location.

Expected result

Container data to be visible across the network.

Actual result

Container data only visible on client that imports it.

Configuration information

Client is OS X 10.8.2, running Filemaker Advanced Pro 12.02
Server is OS X 10.8.1, running Filemaker Server 12.02
Container storage area is relative the Server database directory