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
Creating a database solution 4-11
• How to use your Help system
• How to use What’s This? Help (Windows)
• How to start the database solution (see “Starting your runtime
database solution” on page 7-5)
• What to do in case of a damaged file (see “Recovering damaged
files” on page 7-6)
• How to reach you for technical support
You might also want to include the following recommendations:
• Tell your users not to rename any solution files (except the runtime
application), or they may be unable to run your solution.
• Recommend that users back up their data regularly. You might
want to automate some of the process by including scripts that save
copies of the solution files.
For more information on automating a backup procedure, see the
FileMaker Pro Help.
Important In the event that your runtime database solution files
become damaged, make sure users have access to your technical
support e-mail address or telephone number in your printed
documentation or in a text file. If a database file is damaged, they
may not be able to access the About layout in your solution to find
out how to contact you.
Design tips for cross-platform solutions
If you’re developing a database solution to be run on both Windows
and Mac OS machines, there are many issues that require planning
and consideration—for example, which font technology, colors, and
design conventions to use.
Creating a consistent appearance
To ensure a consistent look for files across platforms, try to use the
same font technology, for example TrueType. It is best to use fonts
with identical names, styles, and metrics on both platforms. When
fonts used to view a file are different from the ones used to create the
file, there can be problems with word wrapping and placement.
Most font vendors supply Windows and Mac OS versions of the
same font. Contact your font vendor for more information.
When you move a file from one platform to another, if the font used
to create the file isn’t available, another font will be substituted. In
FileMaker Pro for Windows, you can specify how fonts are
substituted in the Microsoft Windows Registry Editor. You can add
more fonts to the Registry Editor to include more font substitutions.
If there is no match and no substitute is defined, FileMaker Pro
changes the font to Arial. In the Mac OS, FileMaker Pro attempts to
substitute a similar font.
Simulating outline and shadow text styles
The Windows platform doesn’t offer outline and shadow text styles.
If you want a shadow effect for titles or headings, simulate the look
by positioning two copies of a text block so that the foremost copy
appears to cast a shadow against your layout.
Simulated text styles as
displayed on the Mac OS
Actual text styles as displayed
on the Mac OS
Simulated text styles as
displayed on the Windows OS
Actual text styles as displayed
on the Windows OS