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
2-12
Developer’s Guide
Important Selecting this option permanently removes access to these
menu commands for all database files in the solution, whether
they’re opened in a runtime application or in FileMaker Pro. This
will help protect your files from password hackers. Structural
elements of the files cannot be modified by anyone, including
FileMaker, Inc. employees. The only way to modify field definitions,
relationships, scripts, or access privileges is by returning to the
original file before it was customized by the Developer Tool.
Consider the long-term needs of your users when defining access
privileges. Communicate their access privileges to them clearly in
the About layout and follow the rules specified by FileMaker, Inc.
See “Adding a custom script to an About menu command” on
page 2-12 and “Your responsibilities as a developer” on page 3-15
for information.
Steps for preventing database modification
To create a database solution that cannot be redesigned or modified,
do the following:
1. Close all of your database files that you are going to customize.
2. Start the FileMaker Developer Tool application and click Next.
3. Select Permanently prevent modification of database structure, select
other options as desired, and click Next.
4. Specify the database files that you want to customize, rename
them if desired, and click Next to go through the rest of the screens
depending on what other options you selected.
5. Specify the location for the solution files, rename the folder if
desired, and click Finish.
The Developer Tool creates a duplicate copy of the database files
with design access removed and places them in a new solution
folder.
Customizing the About, Help, and
Scripts menus
You can customize the menu bar in your database solution to display
a custom script as a menu command in the Help menu or Apple (4)
menu (Mac OS), or to display a custom name for the Scripts menu.
The custom settings are stored in the primary file of your solution.
For information about designing the primary file for your solution,
see chapter 3, “Preparing files for a custom solution.”
Adding a custom script to an About menu command
Use the FileMaker Developer Tool to add a custom script to the
About menu command in FileMaker Pro or your runtime application
that goes to an About layout for your solution. When the Developer
Tool processes your database files, it creates a menu command
named “About <your solution>” and places it in the Help menu
(Windows) or Apple (4) menu (Mac OS).
Custom About command in
FileMaker Pro (Windows)
Custom About command in a
runtime application (Windows)
Custom About command in
FileMaker Pro (Mac OS)
Custom About command in a
runtime application (Mac OS)