Help

Using FileMaker Pro Advanced tools
F
ILEMAKER PRO HELP 601
• how to use your Help system
• how to start the database solution (see Starting runtime solutions (FileMaker Pro
Advanced))
• what to do in case of a damaged file (see Recovering runtime files (FileMaker Pro
Advanced))
• how to reach you for technical support
Important In the event that your runtime database solution files become damaged, make
sure users have access to your technical support email address or telephone number in
your printed documentation or in a text file. If a database file is damaged, they may not be
able to access the About layout in your solution to find out how to contact you.
You might also want to include the following recommendations:
• Tell your users not to rename any solution files (except the runtime application), or they may
be unable to run your solution.
• Recommend that users back up their data regularly. You might want to automate some of
the process by including scripts that save copies of the solution files. For more information,
see
Maintaining and recovering FileMaker Pro databases.
Related topics
About creating runtime solutions (FileMaker Pro Advanced)
Preparing files for a runtime solution (FileMaker Pro Advanced)
Binding files into a runtime solution (FileMaker Pro Advanced)
Naming runtime solutions (FileMaker Pro Advanced)
About creating runtime solutions (FileMaker Pro Advanced)
With FileMaker Pro Advanced, you can bind FileMaker database files into runtime solutions, which
are solutions that do not require FileMaker
Pro or FileMaker Pro Advanced in order to be used on a
computer. You can also create runtime solutions in Kiosk mode.
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:
• a primary database file that connects all of the auxiliary files
• scripts and buttons to open auxiliary files, return to the primary file, display a splash screen
layout at startup, or quit a runtime application
• common elements and a consistent appearance for cross-platform solutions
• tooltips and custom menus
• an About layout to introduce your solution
• a custom Help system that provides usage tips for your solution
• multiple privilege sets that can specify levels of access to layouts, menus, specific tables,
record, fields, and so on
• password-protected accounts assigned to privilege sets that determine the level of access
of account users
Note FileMaker Pro and FileMaker Pro Advanced now allow you to include as many database
tables as you need in a database file. This capability eliminates one of the main reasons for using
multiple files. However, other elements, like scripts and access privileges, are stored at the file level
and so some complex solutions will still benefit from using multiple files.