72 FileMaker Pro Advanced Development Guide
Converting and upgrading solution files
If you have developed a FileMaker Pro runtime database solution
using the Solutions Development Kit (SDK) for FileMaker
Pro 3.0 or
earlier, the Binder utility in the FileMaker
Pro 4.0 Developer Edition,
or the Developer Tool in FileMaker Developer 5.x and 6.0, you can
upgrade your solution and provide your users with the converted files.
Files bound to a runtime application using the earlier tools must be
rebound using the Developer Utilities.
You must convert FileMaker Pro files created in version 6.0 or earlier
to the new file format. You can convert a single file or convert
multiple files at once. For more information about converting files,
see the conversion information in the
FileMaker Pro User’s Guide.
Once you have converted the files, you can upgrade them to take
advantage of newer FileMaker
Pro and FileMaker Pro Advanced
features. If necessary, create scripts to import users’ existing data from
the old runtime database solution into the new, upgraded solution. Use
the Developer Utilities to bind the solution files into a new, upgraded
runtime database solution. See
“Binding databases into runtime
database solutions” on page 68.
Distribute the new upgraded runtime database solution and provide
instructions for how users can upgrade their files by converting the old
files in the new runtime application and importing their data.
Importing data into upgraded runtime solutions
You can include scripts in the new runtime database solution files that
allow users to import records from the old runtime files. The old files
must first be converted to the new file format.
Note When creating your upgraded runtime solution, use a different
extension than the one you used for your old runtime solution.
To prepare your upgraded solution for importing data:
1. Create a folder named “Old Solution Files” inside the folder that
contains the new runtime solution database files.
2. Place copies of the old runtime solution database files in the “Old
Solution Files” folder.
3. In each upgraded file, create a script to convert the old solution file
and import records from it to the new file.
The functionality of the script should include:
1 Convert File [<filename of the old version of the solution file>]
1 Import Records [<old filename with the new solution’s extension>]
1 Close File [<old filename with the new solution’s extension>]
4. Add a button to activate the script.
5. Repeat steps 3 and 4 for each upgraded file.
6. Use the Developer Utilities to bind your upgraded solution files
into the new runtime database solution.
7. Test your buttons in the runtime application.
Use sample data to make sure the records import properly and data is
imported to the correct fields.
8. Distribute the new solution files that contain the buttons.
9. Provide instructions telling users how to import data into the new
solution files.
Users can copy their old files into the “Old Solution Files” folder and
use the buttons in the new files to convert the old files and import
records from them into the new solution files.
