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
Customizing your database solution
2-11
Renaming your databases
Use the FileMaker Developer Tool to rename all the files in your
database solution and automatically update all internal reference
links (filespecs) to related files and scripts. The Developer Tool
creates a duplicate copy of the database files before it renames them
and updates the links.
Procedure for renaming files
To rename your database files and update reference links, 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 Rename files and update internal links, and click Next.
4. Specify the database files that you want to customize, then select
each file in the list and click Rename.
5. In the Rename dialog box, type a name for the new file, and click
OK.
Note If you want the .fp5 extension to be added automatically to the
new filenames, select the Add or remove FileMaker Pro extension
option in step 3 and choose Add .fp5 from the pop-up menu.
6. When you’ve finished renaming all of the specified files, click
Next.
7. Specify the location for the files, rename the new solution folder
if desired, and click Finish.
The Developer Tool creates a duplicate copy of the database files
with the new filenames and updated internal links, and places them
in a new folder.
Choosing filenames for your database solution
When choosing filenames for your database solutions, consider the
platforms on which your solution will be used so your scripts and
lookups will work properly.
Windows filenames may not start with a space. Also, for cross-
platform compatibility, do not use the following characters in
filenames: period (.), quotation mark ("), slash (/), backslash (\),
brackets([ ]), colon (:), semicolon (;), vertical bar (|), equal sign (=),
or comma (,).
Removing design access to your databases
Use the FileMaker Developer Tool to prevent users from altering the
design and structure of your database files and from changing any
passwords or groups that you’ve set up. By specifying the
Permanently prevent modification of database structure option for your
custom solution, users can’t access the following menu commands in
FileMaker Pro:
1 File menu > Define Fields
1 File menu > Define Relationships
1 View menu > Layout Mode
1 Scripts menu > ScriptMaker
1 File menu > Access Privileges
Platform Filename support
Mac OS 31 characters
Windows 95 255 characters, including path
Windows 98 255 characters, including path
Windows NT 255 characters, including path