External container data

The developer tool doesn't move or modify container data that is stored externally, so keep the following in mind:

• Before you open the target file after using the tool, make sure the target is in the same location as the source file relative to the external container data. This ensures that references to external container data will work.

• If the source file is hosted, use Admin Console to close the file, run the tool, and rename the target file to match the source file's name. Next, use Admin Console to remove the source file on the host. Then use FileMaker Pro or the developer tool to upload the target file and its external container data to the host. If you prefer not to download and upload a large amount of external container data along with the file, you can manually transfer only the database file. See Uploading database files manually in FileMaker Server Help

  To upload database files without uploading their external container data, use the --uploadDatabases subcommand with the -without_remote_container option. See Command-line parameters.

• If, during developer tool use, container field storage options are changed (for example, from open storage to secure storage), the FileMaker developer tool does not transfer the container data. To transfer the container data, open the target file with FileMaker Pro and click Transfer Data in the Manage Containers dialog box.