Developer’s Guide

2-2 FileMaker Pro Developer’s Guide
1 Use a binding key you will remember. If you need to add or update
auxiliary files later, rebind the file 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.
Important For additional considerations before binding, see chapter 3,
“Preparing and managing runtime solutions.”
Binder and runtime terminology
This guide uses the following terms when describing the process of
creating runtime applications:
Term Refers to
FileMaker Pro Developer
Edition
The Binder application and other files on both Developer
Edition CD-ROMs
FileMaker Pro application The standard version of the FileMaker Pro application
FileMaker Pro Binder The application that generates the FileMaker Pro runtime
application and binds it to your solution files
FileMaker Pro runtime
application (or “runtime
application”)
The runtime engine you distribute with your solution files
Solution files Your primary file and any auxiliary files
Primary file The database file that the runtime application opens first
Auxiliary file Any additional files, such as import files and relational files
Bundled solution Your solution files, the runtime application, and additional
support files such as DLLs on Windows, optional data and
graphics file filters, and spell-checking software
Bind The process of creating the runtime application and linking
it to the solution files
Binding key A code used when binding the solution files to internally
link the solution files with the runtime application
Three-character extension Associates solution files with the runtime application
Kiosk mode A unique interface that hides operating system elements and
FileMaker Pro standard menus and commands
Cross-platform file A file that has been designed to run in both Windows and
the Mac OS