Developer’s Guide

2-18 Developer’s Guide
It’s a good idea to use sample data to make sure the records are
importing properly and data is going to the correct fields. Test the
data on another machine to make sure the external scripts work.
8. Distribute the new solution files that contain the Import scripts.
9. Provide instructions telling users how to import data into the new
solution files and set appropriate time expectations. If their solution
files are large, the conversion and import process may be lengthy.
Use file size information to calculate how much disk space is
necessary for the conversion to go smoothly. Keep in mind that when
users open an old solution file from the new runtime application, the
file is copied before it’s converted. So, if a solution file is 2 MB,
users will need at least 4 MB available to convert it.
When users execute the Import script, the runtime application finds
the original solution file, converts it, then imports the records into the
new solution file. During the script, the runtime application
temporarily converts a copy of the old file to the FileMaker Pro 5.5
runtime version, and deletes it when the original file is closed. Your
users should delete the original solution files after making a backup
copy of the new solution files.