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
Distributing your bundled solution 4-3
The 4winsys folder
If your solution will be used in Windows 3.1 or Windows NT 3.51, you
must include the 4winsys folder and its contents with your solution. It
contains files that are necessary for the “3-D” look and feel. When the
runtime solution is first opened, the appropriate file will be copied to the
\Windows\System folder, and the 4winsys folder will be deleted. When
the solution is opened in Windows 95, Windows 98, or Windows NT 4.0
or later, the 4winsys folder is unnecessary and is automatically deleted.
End users running Windows 3.1 or Windows for Workgroups 3.11 must
install Win32s version 1.30c before opening the runtime application.
The Developer Edition includes a copy for you to redistribute on the
Developer Edition CD-ROM in the FileMaker Pro 4.0 folder. For more
information on Win32s, see “Installing Win32s” on page 4-9.
Mac OS runtime solution files
For the Mac OS, the minimum files required to run FileMaker Pro
runtime solution files are:
1 the runtime application
1 your bound solution files
Installing items from the Runtime Files folder
Items in the Runtime Files folder (Windows and the Mac OS) should be
distributed along with your bound solution files and the runtime
application to enable additional features, such as spell-checking and data
and graphics importing.
To distribute the Runtime Files folder contents, drag the Runtime Files
folder items from the CD-ROM into the root level of your solution
folder. When the runtime application is first opened, these items will be
moved to the appropriate locations on your end user’s hard disk.
Installing Runtime Files in Windows
Drag the Developer Edition CD\FileMaker Pro
Binder\Runtime Files\System folder into the root level of
your solution folder. The files should immediately work with the
Runtime application on the end user’s hard disk.