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
Creating a database solution 4-15
Creating platform-specific scripts
Although most ScriptMaker steps work on both platforms, some
script steps rely upon platform-specific features. The following steps
are platform-specific:
Windows-only script steps
• DDE Execute
• Send Message
• Insert Object
• Update Link
Mac OS-only script steps
• Send Apple Event
• Perform AppleScript
• Speak
The Windows Print Setup script step is translated to the Mac OS
Page Setup script step, and vice versa. Note that print options depend
on the printer driver, so that options you save with a script on one
machine may not be available on another. The Send Message script
step (Windows) is translated to the Send Apple Event script step
(Mac OS), and vice versa.
Other platform-specific script steps are skipped when run on a
different platform. Also, platform-specific script steps are shown in
italics when viewed on a different platform.
Your responsibilities as a developer
FileMaker, Inc. has a policy of established procedures for decoding
and repairing passwords. If a customer complies with these
procedures, then FileMaker, Inc. may decode passwords, and/or
supply data or a repaired file for the customer.
If you distribute FileMaker Pro runtime files with passwords, or you
have removed master level design access and you do not want
FileMaker, Inc. to decode passwords, repair access privileges, and/
or return data to a customer who requests such services, you must do
the following:
1. Notify your customers in writing and keep a record of such notice
that your database solution contains passwords and/or data that can
only be provided by you.
2. Every file in your runtime database solution must contain an
About layout accessible from any layout in the database.
See “Adding a custom script to an About menu command” on
page 6-11 and “Creating an About layout” on page 4-8.
3. The layout name must begin with the word “About.”
4. The About layout must contain these items:
• Solution Name
• Your company information: company name, address, city, state,
postal code, country, and phone number
• Your support policy (for example, how and when you are
available for technical support)
5. If your databases contain passwords, and you do not want
FileMaker, Inc. to decode and repair passwords and access privileges
for your database, the About layout must contain this exact warning:
“USER WARNING: This database solution contains password(s) that can
only be provided by the Developer identified above.”
6. If design access has been removed from your database solution by
selecting the Permanently prevent modification of database structure
option in the Developer Tool, then the About layout must contain
this exact warning:
“USER WARNING:This file is not customizable. Contact the above named
Developer for information on customizing this database solution.”