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
10-4 Developer’s Guide
The following is an example of a Microsoft XML DSO applet tag
that you might use in your web page to query FileMaker Pro for
XML data using the FMPDSORESULT grammar—where the “url”
parameter can be any valid FileMaker Pro CGI request containing a
–format parameter equal to “–dso_xml” or “–dso_xml_dtd.” (See
“Generating FileMaker Pro CGI requests for an XML document” on
page 10-8 for a list of valid FileMaker CGI requests.)
<applet code=com.ms.xml.dso.XMLDSO.class width=0 height=0
id=xmldso MAYSCRIPT=true>
<PARAM NAME="url" VALUE=fmpro?–db=PhoneList.fp5&
–format=–dso_xml&–find=>
</applet>
Description of elements in the FMPDSORESULT grammar
Each ROW element in the generated FMPDSORESULT grammar
contains a number of FIELD elements that correspond to the field
names in the specified layout.
Spaces or single colons in field names are converted to underscores
in the element names (for example, <FIRST_NAME>). Double colons
in portal fields are converted to periods (for example,
<PHONE.PHONE_NUMBER>). This is done because colons are
reserved in XML for specifying namespaces and spaces are not
allowed in XML element names.
For repeating and portal fields, each FIELD element will contain a
DATA element that corresponds to each repetition or portal record.
Note The content of container fields in the database will be
generated in the form of the relative URL used for retrieving the
content instead of the actual content (such as an image).
To qualify the XML elements for the FileMaker Pro application, the
names of all elements and attributes in this grammar are associated
with the unique XML namespace http://www.filemaker.com/
fmpdsoresult. This namespace is declared in the grammar as the
default namespace.
The following is an example of XML data generated with the
FMPDSORESULT grammar.
Example of XML data in the FMPDSORESULT grammar
<?xml version="1.0" encoding="UTF-8"?>
<FMPDSORESULT xmlns=“http://www.filemaker.com/fmpdsoresult”>
<ERRORCODE>0</ERRORCODE>
<DATABASE>PhoneList.fp5</DATABASE>
<LAYOUT>Web Layout</LAYOUT>
<ROW RECORDID=“3” MODID=“23”>
<FIRST_NAME>John</FIRST_NAME>
<LAST_NAME>Smith</LAST_NAME>
<PHONE.PHONE_NUMBER>
<DATA>555-444-3333</DATA>
<DATA>555-222-9999</DATA>
</PHONE.PHONE_NUMBER>
</ROW>
<ROW RECORDID=“6” MODID=“32”>
<FIRST_NAME>Barbara</FIRST_NAME>
<LAST_NAME>Jones</LAST_NAME>
<PHONE.PHONE_NUMBER>
<DATA>555-666-7777</DATA>
<DATA>555-333-0000</DATA>
<DATA>555-111-7654</DATA>
</PHONE.PHONE_NUMBER>
</ROW>
</FMPDSORESULT>