Developer’s Guide
Table Of Contents
- Preface Introducing FileMaker Developer 5.5
- Chapter 1 Installing FileMaker Developer 5.5
- What you need to install FileMakerDeveloper
- System requirements for FileMaker Developer 5.5
- Networking requirements
- Web publishing requirements
- Requirements for advanced features (Windows)
- Requirements for advanced features (MacOS)
- Installing FileMaker Developer 5.5 in Windows
- Installing FileMaker Developer 5.5 in the MacOS
- New features in FileMaker Pro
- FileMaker Pro 5.5 and Mac OS X
- Contents of the FileMaker Developer 5.5 folder
- Contents of the Developer Extras folder on the FileMaker Developer 5.5 CD
- Read Me file
- Electronic documentation
- Abiding by the license agreement
- Registration and customer support
- About the TechInfo database
- Chapter 2 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 yoursolution
- Converting and upgrading solution files
- Chapter 3 Creating custom layout themes
- Chapter 4 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 Scriptsmenus
- Adding the FileMakerPro extension to database filenames
- Saving your settings in the Developer Tool
- Chapter 5 Distributing FileMakerPro runtime database solutions
- Chapter 6 Publishing your database on the Web
- Types of web publishing
- Using the FileMakerPro 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 networkconnection
- Opening password-protected databasesremotely
- 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 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
- 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 9 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 10 Understanding external function plug-ins
- About external functions
- About the plug-in example file
- Installing, enabling, and configuring the exampleplug-in
- Description of the FMExample plug-in’s externalfunctions
- Using the example plug-in
- Customizing the plug-in example
- 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
- Registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMakerPro
- Appendix B Valid names used in CGI requests for FileMakerProXMLdata
- 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 FileMakerPro values for error codes
- Index
4-8 Developer’s Guide
Assigning a three-character filename extension
The three-character filename extension associates all of the solution
files with the FileMaker Pro runtime application. If a user has more
than one runtime database solution on a machine, the filename
extension together with the binding key will ensure that the correct
runtime application is started when a solution file is double-clicked.
Use an extension that is unique to your users’ computer systems.
Assigning the extension for Windows solutions
The three-character extension registers your runtime application
with the Windows operating system. The extension is used by
Windows to determine which application starts when you double-
click a solution file. The Developer Tool appends the extension to all
database filenames in the runtime database solution during the
binding process.
Assigning the extension for Mac OS solutions
In the Mac OS, the three-character extension becomes the creator
code for the runtime application. The creator code must be unique to
ensure that the Mac OS Finder can determine which application
created each document. The creator code is stored in the solution
files and in the runtime application.
Because creator codes are four characters, the Developer Tool inserts
an uppercase “F” after the first character. For example, the default
three-character extension “USR” becomes the “UFSR” creator code.
Creator codes are case-sensitive.
Note Creator codes should be registered with Apple Computer to
verify that the creator code you choose is unique. If the creator code
is not unique, solution files might not open with the appropriate
runtime application. You may use the USR three-character extension
because FileMaker, Inc. has registered the UFSR creator code with
Apple Computer, Inc. Contact Apple Developer Support or visit
their web site at www.apple.com to register any other creator codes.
Conflicts with non-unique filename extensions
If the three-character extension is not unique, it might cause registry
(Windows) or desktop (Mac OS) conflicts. For example, if you use
the .fp5 extension for your runtime database solution and your users
have FileMaker Pro installed on their hard disks, all of their
FileMaker Pro document icons (and the application icon in the
Mac OS) will change to the runtime icons. Additionally,
FileMaker Pro documents will no longer automatically open the
FileMaker Pro application.
Windows To restore the document icons to the original
FileMaker Pro document icon:
1. Discard the runtime application.
2. Open a document in the FileMaker Pro application, then close it
and exit the application.
3. Restart your computer.
Mac OS To restore the document and application icons to the original
FileMaker Pro icon:
1. Discard the runtime application.
2. Rebuild the desktop file: Hold down Option + 3 and choose
Special > Restart. Continue holding down the keys while the
computer is restarting. Then, when it displays an alert dialog box,
click OK to rebuild the desktop.
The .pec filename extension associates
the files with the runtime application