Developer’s Guide

Chapter 2: Binding solution files
This chapter describes how to create the bundled solution you’ll
distribute to your end users. It assumes you have developed and
thoroughly tested the solution files. See chapter 3, “Preparing and
managing runtime solutions,” for more information.
The binding process—an overview
To create a runtime solution using the Binder application, you:
1. Specify the solution’s primary file.
2. Name the runtime application.
3. Assign a binding key.
4. Add any auxiliary files to the runtime solution.
5. Choose additional binding options, such as Kiosk mode.
6. Assign the three-character extension to solution files.
7. Specify the folder where the runtime application and solution files
will be copied.
If your solution will be run in Windows, bind it in Windows. If your
solution will be run on the Mac OS, bind it in the Mac OS. For
cross-platform solutions (solutions running in both Windows and the
Mac OS), bind the files first in one platform, then in the other. For more
information, see “Binding cross-platform solutions” on page 2-20 and
“Design tips for cross-platform solutions” on page 3-8.
Before binding
FileMaker, Inc. recommends Before you bind, keep the following
suggestions in mind:
1 Save the original copy of all files before binding. This is especially
important if you bind the solution in Kiosk mode or select the
Permanently remove access to Define Fields, Define Relationships,
ScriptMaker, and Access Privileges option, since both features could
render the solution files permanently unmodifiable.
1 Close all solution files. To bind a file that is already being hosted on
a network, close the file from the host computer before binding.