Developer’s Guide (Mac OS)

Table Of Contents
Preparing solution files 3-15
3. Create scripts that import data from the old filename (Address) to the
new filename (Address2). Although you’re working in FileMaker Pro
3.0, the scripts you are creating will work with your end-user’s 2.x
solution files.
If your end-users only want to import a subset of the records in the
2.x file format, you should create a script that opens the database,
goes to Find Mode and pauses. They then search on the criteria they
choose. The script should then continue by importing the found set.
Important Make sure that the path to the old file (Address) is similar
on your machine and your end-user’s machines. For example, if your
solution files are in the same folder, your new solution file, Address2,
will need to be in the same folder as your end-user’s solution files.
4. Test your scripts carefully. It is a good idea to use sample data to
make sure the imports are working properly and data is going to the
correct fields.
5. Distribute only the new solution files (Address2). The end-users will
run the script, which finds the 2.x Address file and imports the
records into the Address2 file. During the script, the runtime
application temporarily converts a copy of the old file (Address) to
FileMaker Pro 3.0, and deletes it when the converted file is closed.
Now your end-users should start using the new solution files (Address2).
It is recommended that they delete the old solution files after making a
backup copy.
Keep the following tips in mind:
1 Provide instructions telling end-users how to use your scripts to
convert their solution files and import data into the new solution files.
1 Use file size information to calculate how much disk space is
necessary for the conversion to go smoothly. Keep in mind that a 2.x
file that is opened via a script with the 3.0 runtime engine is copied,
and then converted. For example, if a solution file is 2 MB, you will
need at least 4 MB available to convert their solution.
1 Set appropriate time expectations for your end-users. If their solution
files are large, the conversion process may be very lengthy.