Developer’s Guide
Table Of Contents
- Chapter 1 Welcome to FileMaker Developer
- Chapter 2 Installing FileMaker Developer in Windows
- Chapter 3 Installing FileMaker Developer in the Mac OS
- Chapter 4 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 your solution
- Converting and upgrading solution files
- Chapter 5 Creating custom layout themes
- Chapter 6 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 Scripts menus
- Adding the FileMaker Pro extension to database filenames
- Saving your settings in the Developer Tool
- Chapter 7 Distributing FileMaker Pro runtime database solutions
- Chapter 8 Publishing your database on the Web
- Types of web publishing
- Using the FileMaker Pro 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 network connection
- Opening password-protected databases remotely
- Chapter 9 Custom web publishing using CDML
- About the CDML examples
- General steps for custom web publishing using CDML
- About CDML format files
- Generating FileMaker Pro CGI requests using CDML
- Using the CDML Tool and templates
- About the CDML Reference database
- Creating error messages
- Using an encoding parameter with a CDML replacement tag
- Planning your web site
- Chapter 10 Using FileMaker Pro XML to deliver your data on the Web
- About the XML examples
- General process for custom web publishing using XML
- Generating an XML document
- Using the FMPDSORESULT grammar
- Using the FileMaker Pro Extended XML grammars
- About UTF-8 encoded data
- Generating FileMaker Pro CGI requests for an XML document
- Using style sheets with your XML document
- Comparing CSS, XSLT, and JavaScript
- Looking at the XML Inventory example
- Chapter 11 Using JDBC to deliver your data
- About the JDBC examples
- About JDBC
- Using the FileMaker JDBC Driver
- SQL supported by the FileMaker JDBC Driver
- FileMaker Pro support for Unicode characters
- About the FileMaker JDBC Driver interfaces and extensions
- Example 1: Looking at the FileMaker Pro Explorer application
- Example 2: Creating the JBuilder Inventory application
- Example 3: Creating the Visual Cafe Inventory application
- Chapter 12 Understanding external function plug-ins
- About external functions
- About the plug-in example file
- Installing, enabling, and configuring the example plug-in
- Description of the FMExample plug-in’s external functions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing an external function plug-in
- FileMaker Pro messages sent to the plug-in
- Debugging your plug-in
- Avoiding potential Mac OS resourceconflicts
- Providing documentation for your plug-in
- Registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMaker Pro
- Appendix B Valid names used in CGI requests for FileMaker Pro 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
- 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 FileMaker Pro values for error codes
- Index
8-18 Developer’s Guide
To set up your computer to act as a single-machine network, enable
and activate TCP/IP networking. On Windows machines, this is
usually already set up for you (if you can connect to the Internet, then
TCP/IP networking is active). On Mac OS machines, one way to set
up TCP/IP networking is to create a new TCP/IP control panel
configuration that connects via Ethernet to any IP address manually.
(For information on setting up TCP/IP networking, see the
documentation that came with your operating system.)
Once you’ve set up your computer to act as a single-machine
network, you can type http://localhost in your web browser
and the FileMaker Pro Web Companion will serve the HTML pages
that are located in the Web folder as well as any open databases that
are shared via the Web Companion—without connecting to the
Internet or intranet.
Tip To thoroughly test your web site, click on every link that exists
in your custom web pages under every possible situation, with your
databases open, with (and without) any records existing in each
database. Did you catch all the errors and create an error message for
each of them?
Opening password-protected
databases remotely
You can open and close FileMaker Pro databases from your web
browser or other client application by making a –dbopen or –dbclose
request to FileMaker Pro.
Note You can also open and close FileMaker Pro databases remotely
by using the DbOpen and DbClose pseudo procedures with the
FileMaker JDBC Driver. See
“Using DbOpen and DbClose pseudo
procedures” on page 11-5 for information.
The databases must be located in the Web folder and the Web
Companion Configuration dialog box must have Remote
Administration enabled. In addition, you should require a remote
administration password to ensure that once databases are opened,
they cannot be closed by an unauthorized user.
The Web Companion uses HTTP basic authentication to enforce web
security. When a –dbopen request is made to FileMaker Pro, the
browser or client application displays the basic user name/password
dialog box where you type
admin for the user name and the remote
administration password that you specified in the Web Companion
Configuration dialog box.
For databases that also have an access privileges password, you must
use the –password parameter with the –dbopen request. After you
enter the admin user name and remote administration password, the
Web Companion checks the –password parameter in the request.
Tip For better security, place your databases in subfolders within the
Web folder. This way, unauthorized users will not know the rest of
the path even if they gain access to the Web folder.
Opening and closing databases using XML
Here is an example of making a –dbopen request using an XML
document:
FMPro?–db=secretfolder/employees.fp5&–format=–fmp_xml&
–password= dbpassword&–dbopen
Here is an example of making a –dbclose request using an XML
document:
FMPro?–db=secretfolder/employees.fp5&–format=–fmp_xml&–dbclose
For more information, see “Generating FileMaker Pro CGI requests
for an XML document” on page 10-8 and chapter B, “Valid names
used in CGI requests for FileMaker Pro XML data.”