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
Chapter 4: Distributing your bundled solution
The final step in preparing your bundled solution is creating an
installation procedure. You should:
1 organize the files that end users need to use your solution
1 choose how you will distribute your solution, for example on a
CD-ROM, the World Wide Web, or on floppy disks
1 provide end users with documentation for installing your solution
This chapter covers the above, as well as information on running,
updating, and recovering solution files.
Organizing your solution files
Start by gathering all the files that are included in your bundled solution.
These include the bound primary and auxiliary files, the runtime
application, an end-user license agreement (see page 1-12) and, in
Windows, six DLLs created during the binding process. The solution
files are gathered in a folder created during the binding process
(“<Primary filename> Solution Folder”).
Include any optional files that end users might need, such as spell-
checking dictionaries or file filters, in the appropriate folder inside the
solution folder. These optional files are located on the Developer Edition
CD-ROM:
Developer Edition CD\FileMaker Pro
Binder\Runtime Files. See “Installing items from the Runtime Files
folder” on page 4-3 for more information.
Important DLLs and optional files and folders inside the solution folder
cannot be moved or renamed.