Developer’s Guide
Table Of Contents
- Chapter 1: Installing FileMaker Pro Developer Edi...
- Chapter 2: Binding solution files
- The binding process—an overview
- Before binding
- Binder and runtime terminology
- Specifying the primary file
- Naming the runtime solution
- Assigning the binding key
- Choosing auxiliary files
- Choosing binding options
- Assigning the three-character extension
- Specifying a location for solution files
- What happens during binding
- Binding cross-platform solutions
- Changing solutions
- Chapter 3: Preparing and managing runtime soluti...
- Chapter 4: Distributing your bundled solution
- Appendix A: Feature comparison—runtime Appendix ...
- Appendix B: About the TechInfo database
- Index
Binding solution files 2-3
Specifying the primary file
A runtime solution can consist of only one primary file, or a primary file
and a set of auxiliary files. The primary file is the database that the
runtime application opens first. While it can contain data, the primary
file frequently consists of a “Main Menu” layout containing buttons that
navigate end users to other database files (auxiliary files). It should also
contain an “About” layout and a sample Help script. Auxiliary files
interact with the primary file through relationships or external scripts.
To specify the primary file for your runtime solution:
1. Double-click the FileMaker Pro Binder application icon in the
Developer Edition CD\FileMaker Pro Binder folder.
2. Click the Select button to select your primary file.
3. Browse through the contents of your hard disk until you locate the file
you want to be the primary file and select it.
4. Click the Open button (Windows) or the Add button (Mac OS).
Tip You can also use “drag and drop” to specify the primary file by
dragging the primary file on top of the FileMaker Pro Binder application
or into the first panel of the FileMaker Pro Binder application.
Binder application icon
The first panel in the Binder application