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
Distributing FileMaker Pro runtime database solutions
4-3
Solution Extras files for Mac OS solutions
The following table describes additional graphic import filters and
extensions that you can include with your runtime database solution
for Mac OS users.
Copy the Solution Extras folder and its contents from the Runtime
Files folder into the root level of your runtime database solution
folder. When the runtime application is started, the files inside the
Solution Extras 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 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.
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, ClarisWorks, and Excel databases into your runtime
database solution. They will also have access to four spelling
dictionaries.
Cworks.imp Used to import ClarisWorks databases
Dbf.imp Used to import dBASE files
Excel.imp Used to import Excel 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
System folder and files Description
Solution Extras
folders and files Description
Solution Extras folder Contains the Claris and Extensions folders.
Claris folder Contains the Claris Translators folder and the Claris
XTND System file for graphic importing
Claris Translators
folder (inside the
Claris folder)
Contains EPSF PFLT, MacPaint 2.0, and TIFF graphic
import filters
Extensions folder Contains XTND Power Enabler for graphic importing
on Power Macintosh machines, and Microsoft OLE
Automation, Microsoft OLE Extension, and Microsoft
OLE Library files for Excel data importing