Developer’s Guide
Table Of Contents
- Chapter 1 Getting started
- Chapter 2 Using FileMaker Developer features
- Chapter 3 Using the Developer Utilities
- Overview of preparing your solution files
- Modifying database solution files
- Considerations for a runtime database solution
- Binding databases into runtime database solutions
- Saving and reusing Developer Utilities settings
- Converting and upgrading solution files
- Removing full access privileges from databases
- Chapter 4 Distributing runtime database solutions
- Chapter 5 Customizing database solutions
- Chapter 6 Creating custom layout themes
- Chapter 7 Developing third-party FileMaker plug-ins
- About external functions
- About the example plug-in
- Installing, enabling, and configuring the example plug-in
- Description of the FMExample plug-in’s external functions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing external function plug-ins
- FileMaker messages sent to the plug-in
- Avoiding potential Mac OS X resource conflicts
- Providing documentation for your plug-in
- Registering your plug-in
- Appendix A Feature comparison of the runtime application with FileMaker Pro
- Index
46 FileMaker Developer’s Guide
Renaming the Scripts menu
Use the Developer Utilities to rename the Scripts menu for your
database solution. The setting is stored in the primary file of your
solution and the new menu name appears in the menu bar in
FileMaker
Developer and in a runtime application.
Note The menu name must not exceed 30 characters.
To rename the Scripts menu for 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 Scripts
Menu name
.
3. Type a menu name.
Windows To specify a keyboard accelerator, type an ampersand (&)
before the character you want to use as the accelerator key. For
example, type
Re&ports to display the Reports menu with the
letter “p” as the accelerator key.
1. Select other options as required.
2. Click OK.
3. 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.
Database solution with Scripts menu
Database solution with renamed Scripts menu