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
4-8 FileMaker Pro Developer’s Guide
Compressing your solution
If your runtime solution is small, you might consider a compression
application rather than a custom installation application. To compress
files, use a utility such as:
1 WinZip for Windows by Nico Mak Computing, Inc.
(www.winzip.com)
1 StuffIt Deluxe for Mac OS (the StuffIt Expander decompression
utility is available for Windows and Mac OS) by Aladdin Systems
(www.aladdinsys.com)
Note Mention of third-party products is for informational use only and
is not intended to be an endorsement.
Documenting your installation
You’ll need to provide installation instructions to your end users. Keep
the following in mind:
1 Provide written instructions for copying or installing your solution to
your end user’s hard disk.
1 Include software and instructions specifying how your end users will
decompress your solution files.
1 If your end users are installing your solution on Windows 3.1 or
Windows for Workgroups 3.11, provide instructions for installing
Win32s. See the next section, “Installing Win32s.”
1 If your solution might be run on a variety of operating systems, it is
safest to include all optional runtime files.
For more solution documentation tips, see “Documenting your files” on
page 3-4.