Developer’s Guide

Using the FileMaker Developer Tool 4-7
4. Specify the database files that you want to bind, rename them if
desired, and click Next to go to the next screen in the runtime binding
process.
5. Select a primary file.
All of the settings for binding are stored in the primary file. The
primary file opens automatically when a user double-clicks the
runtime application.
6. Select Use custom About script and choose the script’s name from
the pop-up menu.
FileMaker Pro runtime database solutions are required to have an
About layout that gives information about your company and where
users can go for technical support. See “Customizing the About,
Help, and Scripts menus” on page 4-11 for information.
7. Select other options as desired, and click Next.
8. Specify a unique name and binding key for the solution and click
Next.
Note The binding key must be between 6 and 31 characters, and is
case-sensitive.
For more information, see “Specifying a runtime solution name and
binding key” next.
9. Specify a unique three-character filename extension to associate
all of the database files with the runtime application and click Next.
You must specify an extension. For files that will be used on Mac OS
machines, the Developer Tool inserts the letter “F” after the first
character of the extension to indicate a creator code. You should
register the extension as a creator type with Apple Computer. See
“Assigning a three-character filename extension” on page 4-8.
10. Specify the location for the runtime database solution files,
rename the folder if desired, and click Finish to bind the files.
To quickly repeat the binding process, see “Saving your settings in
the Developer Tool” on page 4-14.
For information on bundling the necessary files and delivering your
new runtime database solution to your users, see chapter 5,
“Distributing FileMaker Pro runtime database solutions.”
Specifying a runtime solution name and binding key
The runtime name that you specify in the Developer Tool 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 FileMaker Developer Tool uses
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 cross-platform solution, use the same key when
you bind the solution in Windows and in the Mac OS. Also, keep in
mind that the binding key is case-sensitive on both Windows and
Mac OS machines.
Note Use a binding key you’ll remember and record it in a safe
place. (You can do this by saving the Developer Tool Options file—
see “Saving your settings in the Developer Tool” on page 4-14 for
information.) Otherwise, 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.
The runtime name is used for the folder
and application names in this solution