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-2 FileMaker Pro Developer’s Guide
4. Create a Help system that provides usage and navigational tips for
your solution.
The Help files contained in the FileMaker Pro application cannot be
distributed with the FileMaker Pro runtime application. Explore the
sample integrated help system:
Developer Tools\FileMaker
Examples and Tools\Runtime Solution Example. See “Use
custom Help script” on page 2-12 for more information.
5. Use the FileMaker Pro Binder application to bind the primary and
auxiliary files. See chapter 2, “Binding solution files” for more
information.
6. Test your solution for errors.
Go through your solution trying every option, feature, and button. See
“Testing your solution” on page 3-7 for a list of potential problems
when testing solution files.
Important If your solution will be run in both Windows and the
Mac OS, test your solution on both platforms. See “Design tips for
cross-platform solutions” on page 3-8 for cross-platform database
design advice.
7. Create a custom installer.
Since the runtime application doesn’t have an automatic installer,
create an installation procedure for your solution files. If you’re
distributing the bundled solution on floppy disks, you will also need a
utility to decompress and install the files on your end user’s hard disk.
The Developer Tools CD-ROM includes trial installer applications.
Considerations before binding
Here is a list of things to consider and decide as you develop your
solution. It’s best to address these issues before binding the solution.
1 Do you want end users to open and close auxiliary files?
In the FileMaker Pro runtime application, several menu options have
been eliminated, including Open and Close. If you want end users to
open and close auxiliary files, you must provide scripts in your
solution to perform these operations.
The FileMaker Tools and Artwork Sampler database files in the
FileMaker Examples and Tools folder on the Developer Tools
CD-ROM contain sample buttons you can use to make opening and
closing files easier for your end users.