Administrator’s Guide
Table Of Contents
- Preface Introducing FileMaker Pro 5.5 Unlimited
- Chapter 1 Installing the FileMaker Web Server Connector
- Chapter 2 Administering the Web Server Connector
- Chapter 3 Publishing your database on the Web
- Types of web publishing
- Using the FileMakerPro 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 networkconnection
- Opening password-protected databasesremotely
- Chapter 4 Custom web publishing using CDML
- About the CDML examples
- General steps for custom web publishing using CDML
- About CDML format files
- Generating FileMakerPro CGI requests using CDML
- Using the CDML Tool and templates
- Modified CDML tags
- About the CDML Reference database
- Creating error messages
- Using an encoding parameter with a CDML replacement tag
- Planning your web site
- Chapter 5 Using FileMakerPro XML to deliver your data
- About the XML examples
- General process for custom web publishing using XML
- Generating an XML document
- Using the FMPDSORESULT grammar
- Using the FileMakerPro Extended XMLgrammars
- About UTF-8 encoded data
- Generating FileMakerPro CGI requests for an XML document
- Using style sheets with your XMLdocument
- Comparing CSS, XSLT, and JavaScript
- Looking at the XML Inventory example
- Chapter 6 Using Java and JDBC to deliver your data
- About the JDBC examples
- About JDBC
- Using the FileMaker JDBC Driver
- SQL supported by the FileMaker JDBCDriver
- FileMakerPro support for Unicodecharacters
- About the FileMaker JDBC Driver interfaces and extensions
- Example 1: Looking at the FileMakerPro Explorer application
- Example 2: Creating the JBuilder Inventoryapplication
- Example 3: Creating the Visual Cafe Inventory application
- Using the FileMaker Java classes
- Appendix A Valid names used in CGI requests for FileMaker 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
- 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 B FileMaker Pro values for error codes
- Appendix C Enabling the FileMaker Pro Web Companion in MacOS X
- Index
5-4 FileMaker Pro 5.5 Unlimited Administrator’s Guide
<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>
Note If the –lay parameter is not specified in the FileMaker Pro CGI
request, the LAYOUT element is empty and data for every field in
the database is returned. (See “Generating FileMaker Pro CGI
requests for an XML document” on page 5-8 for information.)