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
Preparing and managing runtime solutions 3-7
FileMaker, Inc. is unable to, and will not, investigate any requests to
verify the truth of statements submitted by the requester beyond what is
required by our procedures. This process has been invaluable to
numerous customers who have legitimately been unable to access their
valuable files.
The password protection in a FileMaker file should not be viewed as an
absolute barrier which 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. We therefore recommend 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 your solution
You should verify the functionality of your solution by testing it
thoroughly before and after binding it to the FileMaker Pro runtime
application.
Here are some suggestions for ensuring the quality of your solution:
1 Verify every function and option in your solution. If you’re
developing a cross-platform solution, test it in both Windows and the
Mac OS platforms. See the next section, “Design tips for
cross-platform solutions,” for more information.
1 Make sure your solution does not use a standard feature that is hidden
or disabled in the runtime application. See appendix A, “Feature
comparison—runtime application and FileMaker Pro” for more
information.
1 Verify that the scripts and buttons work as expected. This is
especially important if you are running your solution in Kiosk mode.
1 Verify your installation procedures and test your documentation.
1 Verify that your solution layouts display well on monitors with
different color capabilities and resolutions.
1 Verify that your solution layouts display well on the smallest size
monitor your end users may be using.