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
9-4 Developer’s Guide
Or, web users might click on a submit button in an HTML form
containing the FMPro form action and the following hidden INPUT
elements:
<P><FORM ACTION=”FMPro” METHOD=”post”>
<P><INPUT TYPE=”hidden” NAME=”-db” VALUE=”Employees.fp5”>
<P><INPUT TYPE=”hidden” NAME=”-lay” VALUE=”FormView”>
<P><INPUT TYPE=”hidden” NAME=”-format” VALUE=”results.htm”>
The submit button in the form contains the –findall request name:
<P><INPUT TYPE=“submit” NAME=”-findall” VALUE=”Start Search”>
Request names
The name of a request for CDML data is determined by the name of
the CDML action tag in the request. You use CDML variable tags to
specify the parameters of a request.
Use this request
name (CDML action To generate this request
tag)
–delete Delete record
–duplicate Duplicate record
–edit Edit record
–find Find a record
–findall Find all records
–findany find a random record
–new New record
–dbopen Open database
–dbclose Close database
–view Display format file
Note The -script variable tag (request parameter) is
not designed to work with -view requests.
For a detailed list of the CDML action and variable tags and example
syntax for using them in a FileMaker Pro CGI request, see the Tags
Index in the CDML Reference database (described in
“Using the
Tags tab” on page 9-6).
Requests for adding records to a portal
You can use CDML to add records to a portal of related database
files. When you make an –edit request or a –new request that
includes data for a portal, you must specify the layout and the
relationship name for the related database.
Note You can only add one record at a time to a portal, and therefore
must make separate –new requests to add more rows to the portal.
The following is an example of a –new request for adding a record to
a portal, where “Address::” is the name of the database relationship,
and “City.0” is the related field name in the portal:
FMPro?–db=Employees.fp5&–lay=LayoutOne&FirstName=Sam&
LastName= Smith&Address::City.0=Seattle&–format=reply.htm&–new
Requests for editing multiple records in a portal
You only need to make one –edit request to edit multiple records in
a portal. You specify each row (or record) in the portal by adding a
period and a consecutive number (starting with number 1) to the end
of the related field name.
The following is an example of an –edit request for editing records
in a portal, where “Address::” is the name of the relationship,
“City.1” is the first row in the portal, and “City.2” is the second row
in the portal:
FMPro?–db=Employees.fp5&–lay=LayoutOne&recid=11&
FirstName=Sam&LastName=Smith&Address::City.1=Seattle
&Address::City.2=New York&–format=reply.htm&–edit
The following is an example of another–edit request for editing
records in a portal, in an HTML form:
<FORM ACTION="FMPro" METHOD="POST">