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
4-2
Developer’s Guide
Other solution components that you need to provide include:
1 A license agreement — see “Including a license agreement” on
page 4-4.
1 Installation instructions — see “Documenting the installation
procedures” on page 4-6.
Generated DLL files for Windows runtime
database solutions
The following table describes the Dynamic Link Libraries (DLLs)
that are provided for your runtime database solutions running on
Windows machines. These files are generated by the Developer Tool
during the binding process and must reside in the root level of the
solution folder along with the runtime application and bound
database files.
Important In addition to the generated DLL files, there are two
required DLL files, Shfolder.dll and Comctl32.dll, that need to be
installed separately on your users’ hard disks. These DLLs are
automatically installed by Windows NT 4.0 with Service Pack 3 and
by Internet Explorer 4.0 or later. If your users cannot find either of
these DLLs on their hard disks, you’ll need to instruct them to get
Internet Explorer from the Microsoft web site at
www.microsoft.com.
System files for Windows solutions
The following table describes the data and graphic import files and
spelling dictionaries that you can include with your runtime database
solution for Windows.
Copy the System folder and its contents from the Runtime Files
folder into the root level of your runtime database solution folder.
The files should immediately work with the runtime application on
the user’s hard disk.
Required DLL files Description
Fmeng10.dll Database engine
Fmcor10.dll
Fmfc10.dll
Fmgfx10.dll
Fmint10.dll
Fmnsv14.dll
Fmole10.dll
Fmqte10.dll
Fmwfc10.dll
Fmml10.dll
Fmcon10.dll
XPAL files
Fm_usr.dll Resource file for the filename extension you specified
(.USR by default)
Cllngenu.dll
Clproof.dll
Spelling checker files
Mfc42.dll MFC (Microsoft Foundation Class) file
Msvcrt.dll MSVC runtime file
Ctl3d32.dll Required by MFC
System folder and files Description
System folder Copy folder and its contents into the root level of
the runtime database solution folder—Contains
files for graphics and data import, and four
spelling dictionaries.
Fmbmp32.flt BMP graphic import filter
Fmcgm32.flt CGM graphic import filter
Fmdrw32.flt DRW graphic import filter
Fmmac32.flt MacPaint graphic import filter
Fmpcx32.flt PCX graphic import filter
Fmpic32.flt PIC graphic import filter
Fmsld32.flt Lotus SLD graphic import filter
Fmtiff32.flt TIFF graphic import filter
Fmwmf32.flt Metafile graphic import filter