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
Using FileMaker Pro XML to deliver your data
7-9
Requests for adding records to a portal
When you make an –edit request or a –new request that includes data
for a portal of related database records, 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= –fmp_xml&–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.
–scriptnames Retrieve names of all available scripts for a specified
open, web-shared database
–dbopen Open a database that’s in the Web folder with Remote
Administration enabled
–dbclose Close a database that’s in the Web folder with Remote
Administration enabled
Use these
parameter names To go with these requests
–db (database name) Required for all requests except –dbnames
–lay (layout name) Required for –view, and with –edit or –new requests
for data in related fields and portals. Optional for –
find, –findall
–format Required for all requests. (Use one of these
formats: –dso_xml, –dso_xml_dtd, –fmp_xml, or
–fmp_xml_dtd)
–recid (record I.D.) Required for –edit and –delete. Optional for –find
–modid (modification
I.D.)
Optional for –edit
–lop (logical operator) Optional for –find
–op (operator) Optional for –find
–max (maximum
records)
Optional for –find
–skip (skip records) Optional for –find
–sortorder (sort order) Optional for –find, –findall
–sortfield (sort field) Optional for –find, –findall
–script (perform script) Optional for –find, –findall
–script.prefind
(perform script before
–find)
Optional for –find, –findall
Use this
request name To generate this request
–script.presort (perform
script before sort)
Optional for –find, –findall
–styletype (stylesheet
type)
Optional for all requests
–stylehref (stylesheet
HREF)
Optional for all requests
–password Optional for –dbopen requests. Specifies the
database’s password.
field name (no hyphen) At least one field name is required for –new and
–edit. Optional for –find. See “field name (Name of
specific field)” on page B-10 for more
information.
Use these
parameter names To go with these requests