Transferring container data
When you set up a container field to store data externally, any embedded data in the field is not automatically moved to the external directory. You must transfer the data if you want it stored externally. FileMaker Pro uses the settings you chose in the Options for Field dialog box to move the data to the specified base directory.
In order to be transferred, data must be embedded in the container field or stored externally. Files that are stored by reference and some embedded container data (such as OLE objects, text objects, and layout objects) are not transferred.
You can also transfer data that’s stored externally into the container field, convert data with secure storage to open storage and vice versa, move data between base directories, and move files when the open storage calculation is changed.
You must have full access privileges to transfer data.
To transfer container data:
1.
If you changed storage options for a container field in the Options for Field dialog box (or by right-clicking and choosing Field > Field Options while working in Table View), the Container Data Transfer dialog box appears after you exit the dialog box.
Note  Or, in the Manage Containers dialog box, click Transfer Data. The Container Data Transfer dialog box appears, showing all the container fields that are available for transfer.
2.
To see information about a destination (including whether data is embedded or stored externally, and its base directory, storage type, and file path), click the field (not the checkbox) in the list.
The information appears below the list.
3.
Fields are by default selected for data transfer. To exclude a field from data transfer, deselect the checkbox next to the field.
4.
Click Transfer.
If there is not enough disk space in the base directory, a message appears telling you how much free space is available and how much space is needed. Click OK and create enough space.
FileMaker Pro transfers the data from all selected fields to their destinations.
To stop the transfer process, click Cancel in the Database Update dialog box. Canceling the transfer doesn’t roll back the data already transferred. You can restart the process at any time by following the steps above.
5.
When the transfer is completed, the Transfer Summary dialog box appears, showing you the status, number of files transferred, and number of files skipped. Click OK.
6.
To see a log of the transfer, click Open Log File.
For information about reading this file, see the next section.
Reading the Transfer.log file
The Transfer.log file displays information about container data that failed to transfer.
The most recent data is added to any existing Transfer.log file information, so you may need to scroll to the end of the file to see the results of the latest data transfer session.
From left to right the columns show the date, time, and time zone in which the transfer took place, the filename or error number, and a description of the transfer event.
The following are examples of warnings and errors:
Example 1: Warning
2011-07-20 16:27:58.676 +0800   Warning   [Record ID 3, field Animals::Picture] Skipped non-transferrable data: File reference or text.
Problem: File references and text cannot be transferred.
Solution: For file references, create a script that embeds the referenced files, then transfer data.
Example 2: Error
2011-07-31 11:39:45.265 +0800   Error 301   [Record ID 1] Opening record resulted in error (301): Record cannot be changed, because another user is modifying it.
Problem: A record was being edited when the transfer occurred.
Solution: Turn off file sharing before transferring data.
Example 3: Error
2011-07-31 11:43:06.916 +0800   Error 852   [Record ID 6, field Animals::Picture] Saving container data resulted in error (852): Cannot write file to the external storage.
Problem: The destination path could not be written to.
Solution: Change the operating system permissions for the destination folder.
Was this topic helpful? Send feedback.