Developer’s Guide
Table Of Contents
- Chapter 1: Installing FileMaker Pro Developer Edi...
- Chapter 2: Binding solution files
- The binding process—an overview
- Before binding
- Binder and runtime terminology
- Specifying the primary file
- Naming the runtime solution
- Assigning the binding key
- Choosing auxiliary files
- Choosing binding options
- Assigning the three-character extension
- Specifying a location for solution files
- What happens during binding
- Binding cross-platform solutions
- Changing solutions
- Chapter 3: Preparing and managing runtime soluti...
- Chapter 4: Distributing your bundled solution
- Appendix A: Feature comparison—runtime Appendix ...
- Appendix B: About the TechInfo database
- Index
Preparing and managing runtime solutions 3-3
1 Is the runtime application operating in Kiosk mode?
If your solution is running in Kiosk mode, the entire interface must be
accessible via buttons on the layouts. Include an Exit or Quit button
if the file needs to be closed.
1 Does the runtime solution contain auxiliary files?
Place a “Main Menu” button or startup script in each auxiliary file
that moves end users to the primary file. See “Choosing auxiliary
files” on page 2-5 for more information.
1 Should you enable Permanently remove access to Define Fields, Define
Relationships, ScriptMaker, and Access Privileges?
This option changes the structure of the solution files, making Define
Fields, Define Relationships, ScriptMaker, and Access Privileges
unmodifiable by FileMaker Pro. No one will be able to access these
features, including FileMaker, Inc. employees. See “Permanently
remove access to Define Fields, Define Relationships, ScriptMaker,
and Access Privileges” on page 2-9 for more information.
1 Do you want your end users to be able to modify the database?
You can password-protect solution files before binding to prevent end
users from modifying database files. This helps protect the file in case
an end user opens your solution with the FileMaker Pro application.
Without password protection, end users can print or modify your
scripts and field definitions, and make modifications to your solution.
See “Protecting your solution files” on page 3-5 for more information.
1 Is this a cross-platform solution?
Review “Design tips for cross-platform solutions” on page 3-8 for
advice for handling fonts, graphics, and general cross-platform
issues. For binding tips, see “Binding cross-platform solutions” on
page 2-20.
1 How will you provide updates for your end users?
Plan ahead for the time you may want to update your solution files.
You can make the process easier for end users by providing scripts in
your primary file to export and import their data. See “Importing to a
new solution file” on page 3-16 for an overview.
1 Which printers will your end users have?
It’s a good idea to set document margins in FileMaker Pro 4.0 if your
solution will be printed from a variety of printers.