Developer’s Guide (Mac OS)

4-2 FileMaker Pro SDK Developer’s Guide
What happens during binding
A solution can consist of one primary file, or a primary file and a set of
auxiliary files. The primary file is the database that FileMaker Pro
Runtime opens first. Auxiliary files are related or external files that the
primary file interacts with.
During binding, you specify the files that make up your solution. Then
you highlight the primary file, name your solution, and provide the
binding key and three-character extension. The binding key links the
FileMaker Pro Runtime application to your solution files. The
three-character extension associates your solution files for easier
grouping in the folder. It also ensures that the appropriate runtime
application is opened if an auxiliary file is double-clicked. The key, the
three-character extension, and the name of the primary file are
embedded in the FileMaker Pro Runtime application.
The end result of the binding process is a bundled solution—the
FileMaker Pro Runtime application, the primary file, and the auxiliary
files. You then distribute the bundled solution.
Before binding
Claris recommends Before you bind, keep the following suggestions
in mind:
1 Create a folder for your bundled solution.
1 If you intend the solution to run on both Windows and the Macintosh,
follow DOS naming conventions (for example, CONTACTS.USR).
1 Use a key you will remember. If you should later need to add auxiliary
files, you’ll need to rebind using the same key. If you’re developing a
cross-platform solution, use the same key when you bind the solution
on the Macintosh and when you bind it on Windows.
Including solution files
Before binding your primary file, you first specify all the files that you
will include with your solution.
The solution files must be closed before you can bind. To bind a file that
is already being hosted on a network, close the file from the host
computer before binding.