Developer’s Guide

3-2 Developer’s Guide
General steps for preparing your
solution files
Here are some general steps for preparing your database files before
you customize them with the Developer Tool and distribute them to
your users:
1. If desired, create a custom theme for all the layouts in your
database solution. (See chapter 5, “Creating custom layout themes”
for information.)
2. In FileMaker Pro, design, create and test the databases that make
up your solution.
3. If you’re creating a cross-platform solution for Windows and
Mac OS machines, design and test each database file on both
platforms.
4. If necessary, convert files from earlier versions of FileMaker Pro
to FileMaker Pro 5.
5. Decide which database will be the primary file that users open
first.
6. Create scripts and/or buttons for users to navigate from the
primary file to all auxiliary files and layouts in the solution.
7. Create documentation about your database solution, such as an
About layout that describes your company and where users can go
for technical support, and a Help layout that describes how to
navigate and use your solution.
8. Make backup copies of your original files and store them in a safe
place.
9. Use the FileMaker Developer Tool to customize the database files.
(See chapter 2, “Customizing your database solution” for
information.)
10. Test your custom solution for errors—step through your database
files trying every option, feature, and button. If your solution will be
run in both Windows and the Mac OS, test your solution on both
platforms.
11. Plan how your database solution will be distributed to your users
and, if necessary, create a custom installer.
FileMaker Pro runtime applications don’t have automatic installers,
so you’ll need to create an installation procedure for your runtime
database solution files. You may also need a utility to decompress
and install the files on users’ hard disks. See chapter 4, “Distributing
FileMaker Pro runtime database solutions” for information.
Issues to consider before creating a
runtime database solution
Here’s a list of issues to consider as you prepare your database files
for a stand-alone runtime database solution. It’s best to address these
issues before binding the files to the runtime application.
1 Do you want users to open and close auxiliary files?
In the runtime application, several FileMaker Pro menu options have
been eliminated, including File menu > Open and File menu > Close. If
you want users to open and close auxiliary files, you must provide
scripts in your solution to perform these operations. Then, place a
button or startup script in each auxiliary file that returns to the main
layout of the primary file.
The Interface Elements and Artwork Sampler databases included on
the Developer CD contain sample buttons you can use to make
opening and closing files easier for users. See “Using button image
samples” on page 3-5 for information.
1 Will the runtime application operate in Kiosk mode?
If your runtime database solution will display in Kiosk mode, the
entire interface must be accessible via buttons on the layouts. See
“Design tips for navigating in Kiosk mode” next.