Developer’s Guide
Table Of Contents
- Chapter 1: Installing FileMaker Pro Developer Edi...
- Chapter 2: Binding solution files
- The binding process—an overview
- Before binding
- Binder and runtime terminology
- Specifying the primary file
- Naming the runtime solution
- Assigning the binding key
- Choosing auxiliary files
- Choosing binding options
- Assigning the three-character extension
- Specifying a location for solution files
- What happens during binding
- Binding cross-platform solutions
- Changing solutions
- Chapter 3: Preparing and managing runtime soluti...
- Chapter 4: Distributing your bundled solution
- Appendix A: Feature comparison—runtime Appendix ...
- Appendix B: About the TechInfo database
- Index
3-6 FileMaker Pro Developer’s Guide
Policy on decoding and repairing passwords
FileMaker, Inc. has established procedures, and if a customer complies
with these procedures, then FileMaker, Inc. will decode passwords,
and/or supply data or a repaired file for such customer.
This policy is outlined in the FileMaker, Inc. document entitled
“Unlocking Password Protected Files.” This document can be accessed
via the support area of our web site: http://www.filemaker.com or through
the FileMaker, Inc. fax back system: (800) 800-8954 or (408) 987-3900.
FileMaker, Inc. reserves the right to change this policy without notice.
If you have specific questions about these procedures, please contact
FileMaker, Inc.
Developer responsibilities
If you distribute FileMaker Pro files with passwords or if you have
removed master level access, and you do not want FileMaker, Inc. to
decode passwords, repair access privileges, and/or return data to a
customer who requests such services, you must:
1. Notify your customers in writing and keep a record of such notice that
your solutions contain passwords and/or data that can only be
provided by you.
2. Every file in your solution must contain an “About” screen accessible
from any layout in the database. See “Use custom ‘About’ script” on
page 2-10 for more information.
3. The layout name must begin with the word “About”.
4. The “About” screen must contain all of the following items:
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).
1 This exact warning “USER WARNING: This solution contains
password(s) which can only be provided by the Developer
identified above.”
1 If Permanently remove access to Define Fields, Define Relationships,
ScriptMaker, and Access Privileges has been selected in the binding
options, this exact warning must be included: “USER WARNING:
This file is not customizable. Contact the above named developer
for information on customizing this solution.”