Developer’s Guide

Using the FileMaker Developer Tool 4-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 4-10 and
“Protecting your database solution files” on page 2-7 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 4-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 2-11 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 5-7 for more information.
Creating Kiosk-mode solutions
To display your database files in Kiosk mode, you must either bind
your solution database to a stand-alone runtime application, or assign
a limited access password to your solution database, and choose the
Kiosk option.
To display your solution in Kiosk mode:
1. Close all of your database files that you are going to include in your
Kiosk solution.
2. Start the FileMaker Developer Tool application and click Next.
3. Select Open file in Kiosk mode, select other options as desired, and
click Next.
4. If you have already assigned a limited access password to the
database solution, you can choose any other options. If you have not
assigned a limited access password, you must choose Create a stand-
alone runtime solution, in addition to any other options you want.
See “Protecting your database solution files” on page 2-7 for
information about assigning passwords.