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
3-14
Developer’s Guide
The Status (CurrentPlatform) function returns a 1 when run on a
computer using the Mac OS, a 2 when run on a computer using
Windows 95 or Windows 98, and a -2 when run on Windows NT
systems. Use this function with the If script step to perform different
actions depending on the current platform.
If [“Status (CurrentPlatform) = 1]
Perform Script [Sub-scripts, “Print in Mac OS”]
Else
Perform Script [Sub-scripts, “Print in Windows”]
End If
Creating platform-specific scripts
Although most ScriptMaker steps work on both platforms, some
script steps rely upon platform-specific features. The following steps
are platform-specific:
Windows-only script steps
1 DDE Execute
1 Send Message
1 Insert Object
1 Update Link
Mac OS-only script steps
1 Send Apple Event
1 Perform AppleScript
1 Speak
The Windows Print Setup script step is translated to the Mac OS
Page Setup script step, and vice versa. Note that print options depend
on the printer driver, so that options you save with a script on one
machine may not be available on another. The Send Message script
step (Windows) is translated to the Send Apple Event script step
(Mac OS), and vice versa.
Other platform-specific script steps are skipped when run on a
different platform. Also, platform-specific script steps are shown in
italics when viewed on a different platform.
Protecting your runtime database
solution files
To prevent FileMaker Pro users from modifying the structure of your
runtime database solution, define passwords for each database in
FileMaker Pro before binding the files to the runtime application.
Runtime solution files can be opened in FileMaker Pro—if
passwords have not been defined, users can access and modify
scripts, field and relationship definitions, access privileges, and
layouts.
You can permanently remove access to the Access Privileges menu
command after you’ve defined the passwords, as well as access to
other menu commands, by selecting the Permanently prevent
modification of database structure option in the Developer Tool. See
“Removing design access to your databases” on page 2-11 for
information.
Setting a default password
You may want to set a master password that gives you access to the
entire file and another password that gives users limited access. If
most of your users will be using the same password to access your
solution, you can set the password as the default and suppress the
password dialog box from appearing when the file is opened. Then,
to display the password dialog box so you can enter a different
password such as your master password, press Shift (Windows) or
Option (Mac OS) as you open the file.
To set a default password for a database and suppress the password
dialog box:
1. In FileMaker Pro, choose Edit menu > Preferences > Document.