Developer’s Guide

Customizing your database solution 2-9
Note No matter what the filename extensions are, runtime database
files can still be opened in the FileMaker Pro application. To prevent
users from modifying your runtime database solutions, create
passwords for specific access privileges or select the Permanently
prevent modification of database structure option in the Developer Tool
before you bind the files into a runtime database solution. (See
“Removing design access to your databases” on page 2-11 and
“Protecting your runtime database solution files” on page 3-14 for
information.)
Binding files for cross-platform solutions
If your solution will be used in Windows, bind it using the Developer
Tool for Windows. If your solution will be used on the Mac OS, bind
it using the Developer Tool for Mac OS. If you’re creating a cross-
platform solution to be used on both Windows and the Mac OS, bind
the solution files twice: first using FileMaker Developer Tool for
Windows, and then using FileMaker Developer Tool for Mac OS.
Use the same binding key on both platforms. Also, remember that
binding keys are case-sensitive.
When you’re binding database files on a Mac OS machine for a
cross-platform runtime database solution, select the Change filenames
for Windows compatibility option. (See step 18 in “Using the
FileMaker Developer Tool” on page 2-5.)
The Developer Tool automatically updates all files to use the three-
character extension that you specify on this screen and appends the
extension to the filenames. Internal file references used in
relationships, scripts, and external value lists are updated to interact
with the new filenames.
See “Design tips for cross-platform solutions” on page 3-10 for
additional cross-platform information.
Modifying bound runtime files
You can open a bound runtime file in FileMaker Pro to make
modifications to it, for example, to access the Define Value Lists menu
command. However, if you selected the Permanently prevent
modification of database structure option when you bound the files,
then you can’t regain access to these menu commands: Define Fields,
Define Relationships, Access Privileges, Layout Mode, and ScriptMaker.
In this case, you’ll have to open the original database files in order to
make design or structure changes in FileMaker Pro and then rebind
them using the binding key that you assigned to that runtime
database solution.
See “Distributing updates to your runtime database solution” on
page 4-7 for more information.
Displaying databases in Kiosk mode
Use the FileMaker Developer Tool to create a database solution that
displays in Kiosk mode—a special interface that displays your
database on the entire screen with a black background and without
menu commands or window controls.
To make a Kiosk-mode database open automatically in Kiosk mode,
it must be bound to a runtime application or have a password
assigned to it with limited access. See “Opening files in Kiosk mode”
on page 3-3 for more information.
For a demonstration of what a database solution looks like in Kiosk
mode, double-click the Menu.fp5 file located in the Kiosk Solution
Example folder (installed in the Design Tools folder). Leave the
password box blank and click OK.
FileMaker Developer 5 > Design Tools > Examples > Kiosk Solution
Example > Menu.fp5