82 FileMaker Pro Advanced Development Guide
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 “Creating an About layout” on page 79.
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.”
6. If full access privileges have been permanently removed from your
database solution by selecting the
Remove admin access from files
permanently
option in the Developer Utilities, then the About layout
must contain this exact warning:
“USER WARNING: This file is not customizable. Contact the above named
Developer for information on customizing this database solution.”
The accounts and privileges protection in a FileMaker file should not
be viewed as an absolute barrier that will prevent a customer from
accessing files. FileMaker cannot guarantee that a customer will not
be able to identify or bypass the password through third-party
solutions or tools. Therefore, FileMaker recommends that you take
appropriate steps to protect your consulting and development efforts
without relying solely upon the password. For more information about
accounts and privileges, see Help.
If you have a dispute with your customer, you must resolve this
dispute directly with the customer. FileMaker is unable to, and will
not, attempt to resolve such disputes.
Testing before and after creating your solution
You should verify the functionality of your database solution by
testing it thoroughly before and after you customize it with the
Developer Utilities.
To ensure the quality of your custom database solution:
1 Verify every function and option in your solution. If you’re
developing a solution for both platforms, test it on both Windows and
Mac OS X platforms.
1 Make sure your runtime database solution does not use a standard
FileMaker Pro feature that is hidden or disabled in the runtime
application. See
“Feature comparison of the runtime application
with FileMaker Pro” on page 85.
1 Verify that all scripts and buttons work as expected. This is
especially important if you’re displaying your solution in Kiosk
mode. See
“About Kiosk mode” on page 16.
1 Verify your installation procedures and test other instructions in the
documentation.
1 Verify that your database layouts display well on monitors with
different color capabilities and resolutions and on the smallest size
monitor your users may be using.
