Developer’s Guide
Table Of Contents
- Chapter 1 Welcome to FileMaker Developer
- Chapter 2 Installing FileMaker Developer in Windows
- Chapter 3 Installing FileMaker Developer in the Mac OS
- Chapter 4 Creating a database solution
- Overview of preparing your solutionfiles
- Considerations for a runtime databasesolution
- Considerations for Kiosk mode
- Using scripts to control your solution
- Protecting your database solution files
- Providing user documentation
- Design tips for cross-platform solutions
- Creating a consistent appearance
- Simulating outline and shadow text styles
- Using common character sets
- Designing text layouts for cross-platform solutions
- Using a common color palette
- Using graphics in cross-platform solutions
- Using QuickTime movies in cross-platform solutions
- Showing the status bar in Windows
- Using separate scripts for printing
- Using the Status (CurrentPlatform) function
- Creating platform-specific scripts
- Your responsibilities as a developer
- Testing before and after creating your solution
- Converting and upgrading solution files
- Chapter 5 Creating custom layout themes
- Chapter 6 Using the FileMaker Developer Tool
- About the solution examples
- Using the FileMaker Developer Tool
- Binding your databases into a runtime database solution
- Creating Kiosk-mode solutions
- Renaming your databases
- Removing design access to your databases
- Customizing the About, Help, and Scripts menus
- Adding the FileMaker Pro extension to database filenames
- Saving your settings in the Developer Tool
- Chapter 7 Distributing FileMaker Pro runtime database solutions
- Chapter 8 Publishing your database on the Web
- Types of web publishing
- Using the FileMaker Pro Web Companion
- Creating a custom home page
- Creating a custom home page for Instant Web Publishing
- Creating a custom web site using a database layout
- Web Companion support for Internet mediatypes
- Monitoring your site
- Exporting data to a static HTML page
- Testing your site without a network connection
- Opening password-protected databases remotely
- Chapter 9 Custom web publishing using CDML
- About the CDML examples
- General steps for custom web publishing using CDML
- About CDML format files
- Generating FileMaker Pro CGI requests using CDML
- Using the CDML Tool and templates
- About the CDML Reference database
- Creating error messages
- Using an encoding parameter with a CDML replacement tag
- Planning your web site
- Chapter 10 Using FileMaker Pro XML to deliver your data on the Web
- About the XML examples
- General process for custom web publishing using XML
- Generating an XML document
- Using the FMPDSORESULT grammar
- Using the FileMaker Pro Extended XML grammars
- About UTF-8 encoded data
- Generating FileMaker Pro CGI requests for an XML document
- Using style sheets with your XML document
- Comparing CSS, XSLT, and JavaScript
- Looking at the XML Inventory example
- Chapter 11 Using JDBC to deliver your data
- About the JDBC examples
- About JDBC
- Using the FileMaker JDBC Driver
- SQL supported by the FileMaker JDBC Driver
- FileMaker Pro support for Unicode characters
- About the FileMaker JDBC Driver interfaces and extensions
- Example 1: Looking at the FileMaker Pro Explorer application
- Example 2: Creating the JBuilder Inventory application
- Example 3: Creating the Visual Cafe Inventory application
- Chapter 12 Understanding external function plug-ins
- About external functions
- About the plug-in example file
- 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 an external function plug-in
- FileMaker Pro messages sent to the plug-in
- Debugging your plug-in
- Avoiding potential Mac OS resourceconflicts
- Providing documentation for your plug-in
- Registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMaker Pro
- Appendix B Valid names used in CGI requests for FileMaker Pro XML data
- Generating a –find, –findall, or –findany request
- Generating a –view request
- Generating a –new request
- Generating an –edit request
- Generating a –delete request
- Generating a –dbnames request
- Generating a –layoutnames request
- Generating a –scriptnames request
- Generating a –dbopen request
- Generating a –dbclose request
- Generating a -dup request
- Generating an -img request
- Specifying parameters for the request
- –db (Database)
- –lay (Layout)
- –format (Format)
- –recid (Record ID)
- –modid (Modification ID)
- –lop (Logical operator)
- –op (Comparison operator)
- –max (Maximum records)
- –skip (Skip records)
- –sortfield (Sort field)
- –sortorder (Sort order)
- –script (Script)
- –script.prefind (Script before Find)
- –script.presort (Script before Sort)
- –styletype (Style type)
- –stylehref (Style href)
- –password (Database password)
- field name (Name of specific field)
- Appendix C FileMaker Pro values for error codes
- Index
6-14 Developer’s Guide
Renaming the Scripts menu
Use the Developer Tool 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 Pro and in a runtime application.
Database solution with Scripts menu
Database solution with Company Reports menu
The menu name must not exceed 31 characters.
To rename the Scripts menu for your solution:
1. Close all of your database files that you are going to change.
2. Start the FileMaker Developer Tool application and click Next.
3. Select Use custom menu options for the About, Help, or Scripts menu,
and click Next.
Note This option is not available if you selected the Open solution in
Kiosk mode option.
4. Specify the database files, and click Next.
5. Specify the primary file, select Rename Scripts menu, and type the
new name for the menu in the box (1 to 31 characters long). Then
click Next.
Windows To specify a keyboard accelerator, type an ampersand (&)
before the character you want to use as the accelerator key. For
example, type Company Re&ports to display the Company
Re
p
orts menu with the letter “p” as the accelerator key.
6. Specify the location for the new solution folder.
7. Click Finish.
Adding the FileMaker Pro extension to
database filenames
Use the FileMaker Developer Tool to quickly add the FileMaker Pro
filename extension to your database files. For example, if you
created your database files on a Mac OS machine but you now want
the database solution to be used on Windows machines, you can add
the .fp5 filename extension to your database filenames for Windows
compatibility.
To add the FileMaker Pro extension to your database filenames:
1. Close all of your database files that you are going to change.
2. Start the FileMaker Developer Tool application and click Next.
3. Select Add or remove FileMaker Pro extension, choose Add .fp5 from
the pop-up menu, and click Next.
4. Specify the database files, and click Next.
5. Specify the location for the new solution folder.
6. Click Finish.
The Developer Tool creates a duplicate copy of the database files
with the new extended filenames, updates all internal reference links,
and places them in a new solution folder.
Saving your settings in the Developer Tool
You can save the settings you specify in the FileMaker Developer
Tool setup screens and reuse them again. When the Developer Tool
processes your specifications, it automatically creates a text file
named “<Solution Name> Solution Options” and places it in the
same folder that contains the Developer Tool.