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
Distributing FileMaker Pro runtime database solutions 7-3
System folder and files Description
Excel.imp Used to import Excel files
XML.imp Used to import XML files
Claddon.clr- Spelling dictionary that contains computer
terminology
Ukenglsh.mpr- Primary British English dictionary of over
100,000 words that the runtime application uses to
check the spelling
Usenglsh.mpr- Primary US English dictionary of over 100,000
words that the runtime application uses to check
the spelling
User.upr- Spelling dictionary that stores your customized list
of spelling exceptions and additions to the User
dictionary
Solution Extras files for Mac OS solutions
The following table describes additional graphic import filters and
extensions that you should include with your runtime database
solution for Mac OS users.
Note These extension files are for Mac “Classic” OS only. They do
not apply to Mac OS X.
Copy the FileMaker Developer 6\FileMaker Developer Tool\Runtime
Files\Solution Extras\Extensions folder and its contents into the root
level of your runtime database solution folder. When the runtime
application is started, the files inside the Solution Extras\Extensions
folder are automatically copied into the appropriate folders in the
user’s System Folder.
Tip You can add other folders and files to the Solution
Extras\Extensions folder and they will be copied to the appropriate
location in the System Folder on the user’s hard disk. For example,
include a Fonts folder of special fonts for your solution in the
Solution Extras folder, and when the runtime application is started all
fonts are copied into the Fonts folder on the user’s hard disk.
Solution Extras\Extensions files Description
Microsoft OLE Automation Files for Excel data importing
Microsoft OLE Extension
Microsoft OLE Library
FileMaker Extensions files for Mac OS solutions
The following table describes the FileMaker Extensions files you can
distribute with your runtime database solution for Mac OS. With
these files, users will be able to import data from certain versions of
dBASE and Excel databases into your runtime database solution.
They will also have access to four spelling dictionaries.
Copy the FileMaker Extensions folder and its contents from the
FileMaker Developer Tool\Runtime Files folder into the root level of
your runtime database solution folder. When the runtime application
is started, the files should work immediately.
FileMaker Extensions
folder and files Description
FileMaker Extensions Place in same folder as runtime application to enable
folder data importing and spelling dictionaries
DBF Used to import dBASE files
Excel Used to import Excel files
XML Used to import XML files
Claddon.clr
terminology
Spelling dictionary that contains computer