Developer’s Guide
Table Of Contents
- Chapter 1 Getting started
- Chapter 2 Using FileMaker Developer features
- Chapter 3 Using the Developer Utilities
- Overview of preparing your solution files
- Modifying database solution files
- Considerations for a runtime database solution
- Binding databases into runtime database solutions
- Saving and reusing Developer Utilities settings
- Converting and upgrading solution files
- Removing full access privileges from databases
- Chapter 4 Distributing runtime database solutions
- Chapter 5 Customizing database solutions
- Chapter 6 Creating custom layout themes
- Chapter 7 Developing third-party FileMaker plug-ins
- About external functions
- About the example plug-in
- Installing, enabling, and configuring the example plug-in
- Description of the FMExample plug-in’s external functions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing external function plug-ins
- FileMaker messages sent to the plug-in
- Avoiding potential Mac OS X resource conflicts
- Providing documentation for your plug-in
- Registering your plug-in
- Appendix A Feature comparison of the runtime application with FileMaker Pro
- Index
30 FileMaker Developer’s Guide
DLL files for Windows runtime solutions
The Developer Utilities generate a set of Dynamic Link Libraries
(DLLs) during the binding process. These are in the solution folder
along with the runtime application and bound database files. They
must be delivered as part of the runtime solution. If any of these files
are missing or become damaged, they must be replaced.
Extensions folder for Windows solutions
The Extensions folder of Windows runtime solutions contains a
folder for each language supported and a dictionaries folder. Each
language resource folder contains a DLL file for the language
(FMRSRC.dll), a file containing the text for the interface, dialog
boxes, and error messages (FMStrs.dls), and a file containing the
Windows language ID for the language (lang.dat).
The Extensions folder also contains the Dictionaries folder. The
Dictionaries folder contains dictionary files (*.mpr) for all of the
languages supported. The Dictionaries folder also contains a file for
the user spelling dictionary (User.upr).
Choosing a distribution method
After you have organized the files that comprise your solution, you
need to decide how your users will install them. You can distribute
your bundled solution on a CD-ROM, over a network, or via the
Internet.
Reducing solution size
If you are planning on distributing your runtime solution via the
Internet, you may want to reduce the size of the solution before you
package the solution. Deleting dictionaries and language resource
files for languages not supported by your database will reduce the
size of the application.
To reduce the size of your solution:
Windows
1. Open the Extensions folder that is copied to the runtime solution
folder.
2. Delete language resource folders for languages not supported by
your solution.
Important Do not delete the language resource folder for English.
DBConverter.dll omniORB400_rt.dll
DBEngine.dll omnithread30_rt.dll
DOMSupport.dll PlatformSupport.dll
FML10.dll ProofReader.dll
FMLayout.dll ssleay32.dll
FMOLE.dll Support.dll
FMRSRC.dll XalanDOM.dll
FMScript.dll XalanExtensions.dll
FMUserModel.dll XalanSourceTree.dll
FMWrapper.dll XalanTransformer.dll
GdiPlus.dll XCore.dll
HBAM.dll XDraw.dll
libeay32.dll xerces.dll
mfc70u.dll XercesParserLiaison.dll
MFCX.dll XFC.dll
msvcp70.dll XGrfx.dll
msvcp70d.dll XMLEngine.dll
msvcr70.dll XMLSupport.dll
msvcr70d.dll XPath.dll
NSViews.dll XSLT.dll
omniDynamic400_rt.dll XText.dll