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-3
6. Click Next.
7. Drag the database files that you want to customize into the box on
the Specify Solution Files screen or click Add File to locate and add
each file individually.
The Developer Tool will create a copy of every file that is listed in
this box.
Note Make sure to specify every file that’s related to the solution, so
that all internal links between files can be updated. You can specify
as many files as you like, but FileMaker Pro (and FileMaker Pro
runtime applications) can only open up to 50 files at once.
8. If you want to use different names for the final solution files, select
each file in the list and click Rename. In the Rename dialog box, type
a name for the new file and click OK.
Note You do not have to type in a filename extension. However, if
you want the .fp5 extension, you must type it here or select the Add
or remove FileMaker Pro extension option (in step 5) and choose Add
.fp5 from the pop-up menu.
9. Click Next.
The next screen that appears depends on which options you selected
on the Customize Your Solution screen (step 5). If you selected
Create a stand-alone runtime solution, Open solution in Kiosk mode, or
Use custom menu options for the About, Help, or Scripts menu, the
Choose Primary Solution File and Options screen appears. If you did
not select any of these options, then skip to step 21.
Permanently
prevent
modification of
database structure
Create a database solution with the following menu
commands permanently unavailable in FileMaker Pro:
Define Fields, Define Relationships, Access Privileges, Layout
Mode, and ScriptMaker.
Important Once removed, these menu commands cannot
be made available again for the custom solution.
Use custom menu
options for the
About, Help, or
Scripts menu
Create a solution that includes a custom About or Help
menu command or a different name for the Scripts menu.
When you select this option, the Developer Tool presents
a screen on which you can specify script names for the
new menu commands that will display your custom
About and Help layouts, and a new name for the Scripts
menu.
Note This option is not available if you select Open
solution in Kiosk mode.
Add or remove
FileMaker Pro
extension
Add or remove the .fp5 filename extension to associate
files with the FileMaker Pro application. The .fp5
extension is useful for database solutions that will be used
on Windows machines, and is not necessary for solutions
that will only be used on Mac OS machines.
Note This option is not available if you select Create a
stand-alone runtime solution.
Select this
option
To create a copy of your
database files and do this