Developer’s Guide

36 FileMaker Developer’s Guide
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 71.
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 39.
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.
1 Test your runtime database solution with actual data. This is
especially important if users are upgrading from earlier versions of
the runtime application and need to import data into new solution
files.
1 Make sure all the auxiliary files and DLLs (Windows) are present.
1 Show your database solution to intended users to uncover any
usability issues.
1 Install your bundled database files on a completely different
computer to verify that all the files associated with the primary file
can be found.
1 If you’re assigning passwords or permanently removing full
access privileges, test all access levels. Make sure your database
solution contains an About layout that notifies users of the level of
access you’re providing. See
“Creating an About layout” on page 33
and “Your responsibilities as a developer” on page 35.
Important You should keep an unbound version of any runtime
database solution files, especially if you’ve permanently removed
full access privileges. See
“Removing full access privileges
from databases” on page 27.