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
12 FileMaker Developer’s Guide
4. If there are any files that contain tables that you want to exclude
from the report, select the file in the
Available Files list.
The tables in the file appear in the Include fields from tables in selected
file
list. You can then deselect any table in the list.
By default, all tables in all selected files are reported.
5. Clear elements that you want to exclude from the report.
By default, all elements in all selected files are reported. Each
selected element, if present, will be reported on for each selected file.
6. If you do not want the report to be published in the default HTML
format, select XML in the Report Format section.
7. If you do not want the report to automatically open when done,
clear the checkbox for this option in the File Handling section.
8. Click Create.
Using the Script Debugger
Use the Script Debugger to troubleshoot scripts in FileMaker
databases. The Script Debugger enables you to execute your scripts
step-by-step to view issues that may arise as the script is performed.
You control how the Script Debugger steps through the script either
by using the buttons in the Script Debugger window or the
commands in the Debug menu. If you find a step that requires
modification, you can open ScriptMaker
™
from a button in the Script
Debugger window.
Tip To enable the Script Debugger from the Define Scripts dialog
box, press Shift and click the Perform button. To disable the Script
Debugger, press Ctrl (Windows) or Command (Mac OS) and click
the Perform button. For more information on keyboard shortcuts, see
Help.
The Script Debugger recognizes the privileges attached to each
script. A script will only appear in the Script Debugger if you have
editing privileges for the script and the access privileges for the script
are set to Modifiable.
Database Design Report dialog box
Script Debugger window