Developer’s Guide

Distributing runtime database solutions 35
Including printed documentation
In addition to an online Help system, you should include printed
documentation that explains how to install your database solution
and briefly how to use it in case users are not able to open your
solution files.
Other items appropriate for printed documentation include:
1 how to install your bundled solution
1 how to install custom files
1 how to upgrade to new solution files
1 how to use your Help system
1 how to start the database solution (see “Starting runtime database
solutions” on page 32)
1 what to do in case of a damaged file (see “Recovering damaged
files” on page 32)
1 how to reach you for technical support
You might also want to include the following recommendations:
1 Tell your users not to rename any solution files (except the runtime
application), or they may be unable to run your solution.
1 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 Help.
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.
Your responsibilities as a developer
FileMaker has established procedures for repairing files. If a
customer complies with these procedures, then FileMaker may
supply a repaired file to the customer.
If you distribute database files with passwords or you have removed
full access privileges and do not want FileMaker to repair a file for a
customer who requests this service, you must:
1. Notify your customers in writing and keep a record of such notice
that your database solution contains passwords or data that can only
be provided by you.
2. Every file in your runtime database solution must contain an
About layout accessible from any layout in the database.
See “Adding custom scripts to the About menu command” on
page 43 and “Creating an About layout” on page 33.
3. The layout name must begin with the word “About.”
4. The About layout must contain these items:
1 solution name
1 your company name and contact information
1 your support policy (for example, how and when you are
available for technical support)
5. The About layout must contain this exact warning:
“USER WARNING: This database solution contains password(s) that can
only be provided by the Developer identified above.”