68 FileMaker Pro Advanced Development Guide
4. For File Reference Name, type a name. This is the name that will
appear in all lists that display file references.
5. Click OK to save the file reference.
Binding files for both platforms
If your solution will be used in Windows, bind it using the Developer
Utilities for Windows. If your solution will be used on Mac
OS X,
bind it using the Developer Utilities for Mac
OS X. If you’re creating
a solution to be used on both Windows and the Mac
OS X, create two
separate runtime solutions by binding the original solution files twice:
first using FileMaker Developer Utilities for Windows, and then using
FileMaker Developer Utilities for Mac
OS X. Use the same binding
key on both platforms. Also, remember that binding keys are case-
sensitive.
Binding databases into runtime
database solutions
Use the Developer Utilities to produce a stand-alone runtime database
solution that users can access without running FileMaker
Pro or
FileMaker Pro Advanced. The Developer Utilities create a copy of
your files, and bind the database file or files to a runtime application
with a name that you specify.
None of the commands on the Define submenu opened from the File
menu are available in the runtime application. See
“Feature
comparison of the runtime application with FileMaker Pro” on
page 85. The FileMaker Pro Advanced features are also stripped from
the runtime application.
A runtime database can, however, be opened in either FileMaker Pro
or FileMaker Pro Advanced. The full functionality of these
applications will be enabled, except if full access privileges have been
removed. See
“Removing full access privileges from databases” on
page 73.
Runtime database solutions cannot be published over a network, the
Internet, or an intranet unless you use FileMaker Pro or FileMaker Pro
Advanced instead of the runtime application. For a complete list of the
differences between the runtime application and FileMaker
Pro, see
“Feature comparison of the runtime application with FileMaker Pro”
on page 85.
You may need to bind your database files several times before you
prepare them for delivery to your users. When you have completed
development and the final version is bound and ready to distribute,
you should thoroughly test your runtime solution to ensure that it
behaves as expected. See
“Considerations for a runtime
database solution” on page 66.
For information about what users need to use your runtime database
solution, see
chapter 8, “Distributing runtime database solutions” on
page 75.
A startup script in the primary file displays this splash screen layout
