Developer’s Guide

2-16 Developer’s Guide
1 Solution Name
1 Your company information: company name, address, city, state,
postal code, country, and phone number
1 Your support policy (for example, how and when you are
available for technical support)
5. If your databases contain passwords, and you do not want
FileMaker, Inc. to decode and repair passwords and access privileges
for your database, 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 design access has been removed from your database solution by
selecting the Permanently prevent modification of database structure
option in the Developer Tool, 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 password protection in a FileMaker file should not be viewed as
an absolute barrier that will prevent a customer from accessing files.
FileMaker, Inc. cannot guarantee that a customer will not be able to
identify or bypass the password without any assistance from
FileMaker, Inc. Therefore, FileMaker Inc. recommends that you take
appropriate steps to protect your consulting and development efforts
without relying solely upon the password.
If you have a dispute with your customer, you must resolve this
dispute directly with the customer. FileMaker, Inc. 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 Tool.
Here are some suggestions for ensuring the quality of your custom
database solution:
1 Verify every function and option in your solution. If you’re
developing a cross-platform solution, test it on both Windows and
Mac OS platforms. (See “Design tips for cross-platform solutions”
on page 2-11 for information.)
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 appendix A, “Feature comparison of the runtime
application and FileMaker Pro” for information.
1 Verify that all scripts and buttons work as expected. This is
especially important if you are displaying your solution in Kiosk
mode.
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 design
access, 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 2-8 and
“Your responsibilities as a developer” on page 2-15 for information.