Developer’s Guide

Chapter 2
Creating a database solution
You use FileMaker Pro to design and build your database solution,
and FileMaker Developer Tool to bind the Kiosk-mode or
customized stand-alone runtime application. Before you begin to
build your database solution, you need to decide how users will
interact with it.
Your database solution might have any of the following components:
1 a primary database file that connects all of the auxiliary files
1 scripts and buttons to open and close auxiliary files, return to the
primary file, display a splash screen layout at startup, or quit a
runtime application
1 common elements and a consistent appearance for cross-platform
solutions
1 a custom layout theme used for every file in the solution
1 an About layout to introduce your solution
1 a custom Help system that provides usage tips for your solution
1 passwords to protect your databases
The FileMaker Developer 5.5 CD provides an example of a
relational database solution. It includes a primary file, named Main
Menu.fp5, that contains navigation buttons to several auxiliary files
and layouts. Each auxiliary file and layout contains a Main Menu
button to return to the Main Menu layout in the primary file.
If you were to prepare these files for a FileMaker Developer runtime
database solution, you would need to add an About layout to the
primary file, create a script to display the layout, and add a button
that quits the runtime application. (See “Considerations for a runtime
database solution” on page 2-2 and “Creating an About layout” on
page 2-8.)
The Main Menu.fp5 file is in the Developer Extras folder:
\Developer Extras\FileMaker, Inc\Examples\Relational
Overview of preparing your solution files
As you design, build, and test your database solution, keep in mind
how your users will interact with it. This includes navigational
scripts and buttons, effective use of layouts and themes, and Help for
the user.
Main Menu layout of the primary file in the Relational Example