Development Guide
Table Of Contents
- Chapter 1 Introducing FileMaker Pro Advanced
- Chapter 2 Creating database solutions
- Chapter 3 Customizing database solutions
- Chapter 4 Debugging and analyzing files
- Chapter 5 Developing third-party FileMaker plug-ins
- About external functions
- About the example plug-in
- Installing, enabling, and configuring the example plug-in
- Description of the FMExample plug-in’s external functions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing external function plug-ins
- FileMaker messages sent to the plug-in
- Avoiding potential Mac OS X resource conflicts
- Providing documentation for your plug-in
- Appendix A Feature comparison of the runtime application with FileMaker Pro
- Index
Chapter 1
|
Introducing FileMaker Pro Advanced 7
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.
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.”
For more information about creating an About layout, see Help.
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.