Developer’s Guide

Customizing database solutions 45
If you did not bind the files to a runtime application, the Developer
Utilities copy the selected database files to the Project Folder. If you
did bind the files to a runtime application, the Developer Utilities
copy all of the runtime files to a new folder, created inside the Project
Folder and named after the runtime solution.
For more information, see “Creating an About layout” on page 33.
Adding custom scripts to the Help menu command
You can create your own help system for your solution. Create a
Help layout or file and use a script to open it. With the Developer
Utilities, you add the script name to the Help menu. In runtime
applications, the custom Help script command replaces the
FileMaker Developer Help command. For more information, see
“Creating a custom Help layout” on page 34.
To add a custom Help script command to the Help menu in your
solution:
1. Follow steps 1 to 9 in “Modifying database solution files” on
page 18.
2. In the Specify Solution Options dialog box, select Custom Script
for Help menu item
.
3. Select a script from the Script name drop-down list.
4. Select other options as required.
5. Click OK.
6. Click Create.
If you did not bind the files to a runtime application, the Developer
Utilities copy the selected database files to the Project Folder. If you
did bind the files to a runtime application, the Developer Utilities
copy all of the runtime files to a new folder, created inside the Project
Folder and named after the runtime solution.
For more information, see “Creating a custom Help layout” on
page 34.
Custom Help command in
FileMaker Developer (Windows)
Custom Help command in a
runtime application (Windows)
Custom Help command in
FileMaker Developer (Mac OS X)
Custom Help command in a
runtime application (Mac OS X)