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
Chapter 8
Using Java and JDBC to deliver your data
If you’re a Java programmer, you’ll find the new FileMaker JDBC
Driver a welcome addition to FileMaker Developer 5. You can use
this driver with any Rapid Application Development (RAD) tool to
visually create your FileMaker Pro database-aware Java application
or applet.
The previous version of the Developer Edition provided the
proprietary FileMaker Pro 4.0 Java classes (which aren’t supported
by any RAD tool) to use in your Java application’s front end for
retrieving FileMaker Pro data. Now you can use the FileMaker
JDBC Driver to directly access FileMaker Pro data using a RAD tool
as you’re building your code. The Java application or applet that uses
the FileMaker JDBC Driver can access FileMaker Pro data via the
Web Companion.
About the JDBC examples
FileMaker Developer 5 provides three examples of Java applications
that use the FileMaker JDBC Driver to connect to a database. One
example is a development-tool-independent Java application that
was created using the basic Java classes and Sun Microsystems’
Swing 1.1.1. The other two examples are Java front ends created
with the development tools Corel’s (Borland/Inprise) JBuilder 3.0
Professional for Windows and Symantec’s Visual Cafe 4.0 Expert
Edition for Windows.
For step-by-step instructions, see:
1 “Example 1: Looking at the FileMaker Pro Explorer application”
on page 8-8
1 “Example 2: Creating the JBuilder Inventory application” on
page 8-11
1 “Example 3: Creating the Visual Cafe Inventory application” on
page 8-15
The FileMaker Developer CD also includes the proprietary
FileMaker Java classes and examples of Java applets that use them.
For information, see “Using the FileMaker Java classes” on
page 8-17.
For additional information and examples that use Java and JDBC for
general data interchange or for publishing FileMaker Pro data on the
Web, see the product support pages on the FileMaker, Inc. web site
at www.filemaker.com. As a shortcut to the site, double-click
FileMaker on the Web (installed in the FileMaker Developer 5 folder).
About JDBC
JDBC is a Java API for executing Structured Query Language (SQL)
statements, the standard language for accessing relational databases.
JDBC is a trademarked name and not an acronym—although it is
thought of as standing for Java Database Connectivity because it is
the ODBC (Open Database Connectivity) equivalent for Java. JDBC
is a low-level interface, which means that it is used to call SQL
commands directly. It is also designed to be used as a base for higher
level interfaces and tools.
Your Java applet or application can talk directly to the database by
using the JDBC driver to communicate with FileMaker Pro. Your
SQL statements are delivered to the database and the results of those
statements are sent back to you. The database can be located on
another machine (the server machine) connected to the network,
while your Java applet or application is located on your machine (the
client machine). This is referred to as a client/server configuration.