Developer’s Guide
Table Of Contents
- Preface Introducing FileMaker Developer 5.5
- Chapter 1 Installing FileMaker Developer 5.5
- What you need to install FileMakerDeveloper
- System requirements for FileMaker Developer 5.5
- Networking requirements
- Web publishing requirements
- Requirements for advanced features (Windows)
- Requirements for advanced features (MacOS)
- Installing FileMaker Developer 5.5 in Windows
- Installing FileMaker Developer 5.5 in the MacOS
- New features in FileMaker Pro
- FileMaker Pro 5.5 and Mac OS X
- Contents of the FileMaker Developer 5.5 folder
- Contents of the Developer Extras folder on the FileMaker Developer 5.5 CD
- Read Me file
- Electronic documentation
- Abiding by the license agreement
- Registration and customer support
- About the TechInfo database
- Chapter 2 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 yoursolution
- Converting and upgrading solution files
- Chapter 3 Creating custom layout themes
- Chapter 4 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 Scriptsmenus
- Adding the FileMakerPro extension to database filenames
- Saving your settings in the Developer Tool
- Chapter 5 Distributing FileMakerPro runtime database solutions
- Chapter 6 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 7 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 8 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 9 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
- Chapter 10 Understanding external function plug-ins
- About external functions
- About the plug-in example file
- Installing, enabling, and configuring the exampleplug-in
- Description of the FMExample plug-in’s externalfunctions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing an external function plug-in
- FileMakerPro messages sent to theplugin
- Debugging your plug-in
- Avoiding potential MacOS resourceconflicts
- Providing documentation for your plug-in
- Registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMakerPro
- Appendix B Valid names used in CGI requests for FileMakerProXMLdata
- 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 FileMakerPro values for error codes
- Index
Using FileMaker Pro XML to deliver your data 7-3
Note XML data generated by the Web Companion is encoded using
UTF-8 format (Unicode Transformation Format 8). For information,
see “About UTF-8 encoded data” on page 7-7.
About XML namespaces
To avoid name collisions, unique XML namespaces help distinguish
XML tags by the application they were designed for. For example, if
your XML document contains two DATABASE elements, one for
FileMaker Pro XML data and another for Oracle XML data, the
namespaces will identify the DATABASE element for each.
The FileMaker Pro Web Companion generates a default namespace
for each grammar. For example, for the FMPDSORESULT
grammar, the following namespace is generated:
xmlns=“http://www.filemaker.com/fmpdsoresult”
About FileMaker Pro database error codes
The FileMaker Pro Web Companion generates an error code at the
beginning of each grammar based on the current error status of the
database. A value of zero (0) is returned for no error.
<ERRORCODE>0</ERRORCODE>
See appendix C, “FileMaker Pro values for error codes.”
Using the FMPDSORESULT grammar
When you specify “–dso_xml” as the format for a FileMaker Pro
CGI request, the Web Companion will generate XML data based on
a database-specific grammar that uses field names as element names.
The FMPDSORESULT grammar is useful for publishing databases
on web pages that are formatted with cascading style sheets or
XSLT. (See “Comparing CSS, XSLT, and JavaScript” on page 7-11
for information.) The FMPDSORESULT grammar is compatible
with the Microsoft XML Data Source Object used by Internet
Explorer.
The Web Companion will also generate the document type definition
for the grammar if you specify “–dso_xml_dtd” as the format. This
is useful if you want an XML parser to validate the XML before your
document goes to production.
Note Internet Explorer directly supports XML with no additional
software required. The XML can be displayed using dynamic data
binding features available in the browser. This is accomplished with
a Java applet that ships with Internet Explorer 4.0, which presents the
XML as a Data Source Object (DSO) to the browser. With the DSO,
the The Internet Explorer 4.0 browser exposes XML data to scripting
languages such as JavaScript or VBScript via the Microsoft
Document Object Model (DOM). Keep in mind that the Microsoft
XML DSO applet does not provide a mechanism for updating the
data, nor does it know anything about FileMaker Pro database
layouts or value lists.
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 7-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.