Developer’s Guide
Table Of Contents
- Contents
- Chapter 1 Introducing FileMaker Developer 5
- Chapter 2 Customizing your database solution
- About the custom solution examples
- Using the FileMaker Developer Tool
- Binding your databases into a runtime database solution
- Displaying databases in Kiosk mode
- 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 3 Preparing files for a custom solution
- About the Relational Example
- General steps for preparing your solutionfiles
- Issues to consider before creating a runtime database solution
- Opening files in Kiosk mode
- Design tips for navigating in Kiosk mode
- Creating startup scripts
- Using button image samples
- Documenting your database solution
- 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
- Protecting your runtime database solutionfiles
- Testing before and after creating yoursolution
- Converting and upgrading solution files
- Chapter 4 Distributing FileMakerPro runtime database solutions
- Chapter 5 Creating custom layout themes
- Chapter 6 Publishing your database on the Web
- Moving forward using open web standards
- Using the FileMakerPro Web Companion
- Displaying a custom home page
- Using a custom home page with Instant Web Publishing
- Monitoring your site
- Exporting data to a static HTML page
- Testing your site without a networkconnection
- Opening password-protected databasesremotely
- Using the Web Security Database
- 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 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 9 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
- New and 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 10 Writing external function plug-ins
- About the plug-in examples and templates
- Installing, enabling, and configuring FileMakerPro plug-ins
- Using external functions in a calculation
- 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
- Naming and registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMakerPro
- Appendix B 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 C FileMaker Pro values for error codes
- Index
Valid names used in CGI requests for FileMaker XML data
B-7
Optional with: –find requests
Example:
FMPro?–db=employees.fp5&–format= –fmp_xml&
–recid=22&–delete
–modid (Modification ID)
Name/Value Type: Parameter
What it does: Refers to the latest version (incremental counter
number) of the record. This allows you to take necessary measures
to ensure an –edit request is applied to the most current version of the
record, by including a warning and an option to retrieve the most
current record before the –edit request is allowed.
Value is: A modification ID, which is a unique identifier for the
current version of a record in a FileMaker Pro database.
Optional with: –edit requests
Requires: The –recid parameter
Example:
FMPro?–db=employees.fp5&–format= –fmp_xml&
–recid=22&–modid=6&last_name=Jones&–edit
–lop (Logical operator)
Name/Value Type: Parameter
What it does: Specifies how the find criteria are combined as either
an AND or OR –find request.
Value is: Either AND or OR. If the –lop parameter name is not used,
then the find request is assumed to be an AND request.
Optional with: –find requests
Example:
FMPro?–db=employees.fp5&–format= –fmp_xml&
Last+Name=Smith&Birthdate=2/5/1972&–lop=and&–find
–op (Comparison operator)
Name/Value Type: Parameter
What it does: Specifies the comparison operator to apply to the field
name/value pair that follows it in a –find request.
Value is: The operator to use. There are short and long versions of
each operator. The default operator is "begins with". Valid operators
are as follows:
You can use any FileMaker Pro –find operator by specifying the
begins with (bw) parameter. For example, to specify the "Find
Content Match" (= =) operator, you would specify the begins with
parameter (bw) and then you would place the characters "==" before
the actual search criteria. The required lines would look like this:
<input type="hidden" name="–op" value="bw">
<input type="text" name="FirstName" value="= =Sam">
Optional with: –find requests
Requires: A field name and a value
Example:
FMPro?–db=employees.fp5&–format= –fmp_xml&
–op=eq&FirstName=Sam&–find
Short Long FileMaker Pro equivalent operator
eq equals =word
cn contains "word"
bw begins with word*
ew ends with *word
gt greater than > word
gte greater than or equals >= word
lt less than < word
lte less than or equals <= word
neq not equals omit, word