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
4-14 Developer’s Guide
5. Select Make playable on non Apple computers.
The first time you play a movie from another platform,
FileMaker Pro prompts you for the location of the movie. Keep the
files in a common folder and avoid choosing the wrong file—this
could lead to unexpected results.
Showing the status bar in Windows
FileMaker Pro for Windows includes an option to show the status
bar, which allows users to specify whether status bar information at
the bottom of a window is visible or not.
If your layouts are designed to take up most of the available screen
space, users can deselect this option in FileMaker Pro or in your
runtime application to make more room.
Status bar help
To show the status bar:
• Choose View menu > Status Bar.
A check mark next to the menu item indicates that the option is
selected.
Using separate scripts for printing
Scripts that include Page Setup/Print Setup and Print commands are
not 100% compatible across platforms. The print steps in the
ScriptMaker feature rely upon the current printer driver in order to
determine the paper sizes that are available, page orientation, and so
on. Even if a computer using Windows and another using the
Mac OS are connected to the same printer, the drivers themselves are
significantly different—so FileMaker Pro is unable to restore page
setup and print options across platforms.
To work around this, you can do the following:
1. Create separate scripts for Windows and Mac OS. First, open the
file on your Windows machine and create the script for printing from
Windows. Then, move the database file to the Mac OS machine and
create the script for printing from the Mac OS.
2. In ScriptMaker, use the If script step and the Status
(CurrentPlatform) function in both scripts to determine whether to
run the Windows or the Mac OS script. For more information, see
“Using the Status (CurrentPlatform) function” next.
3. Make sure the Perform Without Dialog option for the Print script
step is not selected. This will allow users to change the setup options
before they print.
4. In Layout mode, choose Layouts menu > Layout Setup, select Fixed
Page Margins, and specify margins for Top, Bottom, Left, and Right.
Using the Status (CurrentPlatform) function
FileMaker Pro includes a status function that lets you determine the
platform on which the database solution is being run. This allows
you to perform different script actions such as changing to a different
layout or performing a platform-specific script step. The Status
(CurrentPlatform) function returns an integer value that identifies the
current operating system. For example, the function returns 1 in
Mac OS 9 or earlier, and -1 in Mac OS X. See the onscreen Help for
complete information about integer values.
Use this function with the If script step to perform different actions
depending on the current platform.
If [“Status (CurrentPlatform) = 1]
Perform Script [Sub-scripts, “Print in Mac OS”]
Else
Perform Script [Sub-scripts, “Print in Windows”]
End If