Developer’s Guide

26 FileMaker Developer’s Guide
Modifying a set of solution settings
To modify a settings file:
1. Open the Developer Utilities.
2. Click Load Settings.
3. Locate and select the settings file that you want to modify.
4. Click Load.
5. Specify options.
6. Click Save Settings, then click Save.
7. Click Yes to replace the file.
Your alterations are saved and may be reused again.
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 earlier versions 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
FileMaker Pro User’s Guide and the Converting FileMaker
Databases from Previous Versions
guide.
Once you have converted the files, you can upgrade them to take
advantage of newer FileMaker
Pro and FileMaker Developer
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 22.
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>]