Developer’s Guide (Mac OS)

4-6 FileMaker Pro SDK Developer’s Guide
Assigning the binding key
The binding key internally links the primary file to the FileMaker Pro
Runtime application. It is stored in both the runtime application and the
solution files to ensure that the bound runtime application will only be
able to open the appropriate solution files.
The binding key is case-sensitive on the Macintosh, and must be
between 6 and 31 characters. Use a key you’ll remember and write it
down or record it in a safe place, such as a password-protected
FileMaker Pro database.
If you’re creating a solution for both the Macintosh and Windows
environments, use the same key when you bind on the Macintosh and
when you bind on Windows.
If you don’t want to select additional options, click
Bind to bind your
solution files. FileMaker Pro Binder creates the FileMaker Pro Runtime
application and then links the key to the primary file.
Running your solution in kiosk mode
KioskMaker provides a special interface for your solution. Many of the
standard system interface components are removed, such as the menu
bar and menu commands. The scroll bars are only available if your
layout is larger than one screen. Because much of the FileMaker Pro
Runtime interface is unavailable in kiosk mode, you must create buttons
and scripts for the end-users. See “Using KioskMaker” on page 3-10 for
design tips.
Important If you need to close the files, switch to other applications, or
use a FileMaker Pro Runtime feature available only from a menu
command, you must create a script and provide access to the script from
a button on the layout.
Sharing solution files across platforms
To share a bundled solution over a network of both Windows and
Macintosh computers, follow these steps:
1. Bind the solution files on one platform.
2. Copy the solution files to a computer on the other platform.