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-2 FileMaker Pro Developer’s Guide
Windows runtime solution files
You must copy the following files to the solution folder on the end user’s
hard disk. The minimum files required to run FileMaker Pro runtime
solution files in Windows are:
1 Cllngenu.dll
1 Clspell.dll
1 Fmengine.dll
1 Fmole.dll
1 Fmtools.dll
1 Fm<your extension>.dll
1 the runtime application
1 your bound solution files
The six DLLs are generated during the binding process and
automatically moved into the solution folder.
Mac OS solution folder Windows solution folder
runtime application runtime application
bound solution files
bound solution files
FileMaker Extensions
System
Files for System Folder
Claris
4winsys
Extensions
Control Panels
Data import filters
Items are moved into the
end user’s System Folder
Spell-checking files and data
and graphics import filters
For Windows 3.1 and Windows NT
3.51, items are moved into the end
user’s Windows System folder
6 DLLs generated
during binding
File filter software
Spell-checking files
Sam
p
le Mac OS and Windows solution folders for distribution
Include any control
panels to auto-install