Developer’s Guide
Table Of Contents
- Chapter 1: Installing FileMaker Pro Developer Edi...
- Chapter 2: Binding solution files
- The binding process—an overview
- Before binding
- Binder and runtime terminology
- Specifying the primary file
- Naming the runtime solution
- Assigning the binding key
- Choosing auxiliary files
- Choosing binding options
- Assigning the three-character extension
- Specifying a location for solution files
- What happens during binding
- Binding cross-platform solutions
- Changing solutions
- Chapter 3: Preparing and managing runtime soluti...
- Chapter 4: Distributing your bundled solution
- Appendix A: Feature comparison—runtime Appendix ...
- Appendix B: About the TechInfo database
- Index
Preparing and managing runtime solutions 3-17
4. Create scripts that import data from the original files into the updated
solution files.
The original solution files will be converted when end users execute
the script.
5. 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. Be sure to test the data on another machine to make
sure the external scripts work.
6. Distribute the new solution files that contain the Import script.
The end users will run the script, which 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 FileMaker Pro 4.0, and deletes it when the converted file is closed. End
users should delete the original solution files after making a backup copy.
If your end users only want to import a subset of the records from the
original solution file, they can:
1. Convert the files manually.
The new solution files should contain a script that simply opens
solution files.
2. In the newly converted solution files, perform find requests to locate
the set of records they want imported.
3. In the new solution files, run the scripts you’ve provided that import
data from the converted solution file to the new solution file.
Tip If you have scripts in the original solution files that help your end
users reduce the found set, (for example, a script that Enters Find Mode
and pauses) you can call that script before the import script step.
Keep the following considerations 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
FileMaker Pro 2.x file that is opened via a script with the 4.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 the solution.
1 Set appropriate time expectations for your end users. If their solution
files are large, the conversion and import process may be lengthy.