Developer’s Guide

Using the Developer Utilities 25
Setting the binding key
The runtime name that you specify in the Developer Utilities is used
for the name of the runtime application and can also be used for the
name of the new solution folder that contains the bound runtime
database solution files.
The binding key is a code that the Developer Utilities use during the
binding process to internally link the files with the runtime
application. If you need to add auxiliary files later to the existing
runtime database solution, rebind the files using the same key.
When developing a solution for both platforms, use the same key
when you bind the solution in Windows and in the Mac
OS X. Also,
keep in mind that the binding key is case-sensitive on both Windows
and Mac
OS X machines.
Note Use a binding key you’ll remember and record it in a safe
place. (You can do this by saving the Developer Utilities settings
file: see
“Saving and reusing Developer Utilities settings” on
page 25.) If you forget your binding key and want to change a
runtime database solution, you’ll need to rebind all of the database
files using a new binding key and then redistribute the entire
solution, including a new runtime application.
Modifying bound runtime files
You can open a bound runtime file in FileMaker Pro and
FileMaker
Developer to make modifications to it. However, if you
selected the
Remove admin access from files permanently option when
you bound the files, then you can’t regain access to the Define
Database, Define Value Lists, Define File References, Define
Accounts & Privileges, and Define Custom Functions dialog boxes,
or the
Layout Mode and ScriptMaker menu commands. In this case,
you’ll have to open the original database files in order to make
design changes in FileMaker
Developer and then rebind them using
the binding key that you assigned to that runtime database solution.
See “Distributing updates to runtime database solutions” on page 37.
Saving and reusing
Developer Utilities settings
You can save the settings you specify in the Developer Utilities
dialog box and reuse them again. The settings include the list of files
to be modified. After you have entered your specifications in the
Developer Utilities, click
Save Settings. Choose a location and
filename for the settings file. The extension .sav is automatically
added and should not be changed. You can save as many settings
files as you want, using different locations and names.
Use the Developer Utilities settings file to repeat the same processes
on your database files with the Developer Utilities. When you open
the Developer Utilities, click
Load Settings, locate the settings file,
and click
Load.
T
he runtime name is used for the folder and application names in this solution