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
Publishing your database on the Web
6-15
Now, to test your web published databases, you can type localhost
or 127.0.0.1 in your web browser and the Web Companion will
serve the home page as specified in the Web Companion
Configuration dialog box (see “Displaying a custom home page” on
page 6-5 and “Setting Web Companion configuration options” on
page 6-3).
To return your computer to the original settings after testing:
1. Open the TCP/IP control panel
2. Choose File menu > Configurations.
3. Select the original Default TCP/IP configuration, then click Make
Active.
4. Close the TCP/IP control panel.
5. Repeat these steps for the AppleTalk control panel.
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 8-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 7-8 and appendix B, “Valid names
used in CGI requests for Filemaker XML data.”
Opening and closing databases using CDML
To open or close databases remotely using a –dbopen request or
–dbclose request (CDML variable tags), you must also specify a
–format parameter.