Developer’s Guide

Feature comparison of the runtime application and FileMaker Pro A-7
Appplication Menu command
Window Mac OS Mac OS X
s 9
(Mac OS X only) Pro RT Pro RT Pro RT
Hide Others •
•
Show All •
•
Quit FileMaker Pro
•
Quit <runtime solution>
•
Ignored script steps
Because some features have been removed from the runtime
application, the following script steps are ignored by the runtime
application.
• Print Script Definitions (instead, the current record is printed)
• Print Field Definitions (instead, the current record is printed)
• Open Define Fields
• Open Define Relationships
• Open Define Value List
• Open Sharing
• Open ScriptMaker
• Open Help (executes custom Help script specified during binding)
• Set Multi-User
• New Database
• Perform External Script (if the specified file has not been bound to
the runtime application)
• Open File (if the specified file has not been bound to the runtime
application)
Stored registry settings
On Windows machines, FileMaker Pro stores its registry settings at
hkey_current_user\software\FileMaker\FileMaker Pro\6.0D
The runtime application stores its registry settings at
hkey_current_user\software\FileMaker\<solution name>\6
Note The filename extension for the runtime database files is
registered at hkey_classes_root.
On Mac OS machines, the Developer edition of FileMaker Pro
stores its preferences in the FileMaker Pro 6.0D Prefs file inside the
FileMaker Preferences folder. The runtime application stores its
registry settings in the <Solution name> 6 Prefs file inside the
FileMaker Preferences folder.
On Mac OS X machines, the files are the same except that the
FileMaker Preferences folder is in the <Home>\Library\Preferences\
folder.