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
Distributing runtime database solutions 31
3. Open the Dictionaries folder.
4. Delete dictionaries for languages not supported by your solution.
Mac OS X
1. Open the Extensions folder that is copied to the runtime solution
folder.
2. Open the Dictionaries folder.
3. Delete dictionaries for languages not supported by your solution.
4. Control-click the runtime application package and choose Show
Package Contents.
5. Locate the Resources folder in the Contents folder.
6. Delete language resource folders (*.lproj) for languages not
supported by your solution.
Using a custom installation program
You should use a custom installation program to package your
runtime solution for installation by users. Configuring a custom
installation application to automatically install runtime database
solution files may require more engineering than using a
compression utility, but will help to ensure that your users do not
have difficulties installing your runtime solution.
Here are some custom installation applications that you might want
to use:
1 MindVision Installer VISE (Windows and Mac OS X) by
MindVision, Inc. (www.mindvision.com)
1 InstallShield MultiPlatform (Windows and Mac OS X) by
InstallShield Software Corporation (www.installshield.com)
1 StuffIt InstallerMaker (Mac OS X) by Aladdin Systems
(www.aladdinsys.com)
Using a compression utility program
If your runtime database solution is not complex and you have
confidence in the technical experience of your end users, you might
consider a compression utility program rather than a custom
installation program. To compress files, use a utility such as:
1 WinZip for Windows (Windows 2000, XP) by WinZip
Computing, Inc. (www.winzip.com)
1 StuffIt Deluxe (Windows and Mac OS X) by Aladdin Systems
(www.aladdinsys.com)
Sharing solutions over a network
Users cannot share your runtime database solution over a network
unless they access the files using FileMaker Pro or FileMaker
Developer installed on their machines. You must have a master
password to enable or change network access to the file. For optimal
performance, you can host the solution files using FileMaker Server.
For information about the FileMaker Server and FileMaker Pro
products, and information about volume license sales, see the
FileMaker web site at www.filemaker.com.
What your users need
In order to run your runtime database solution, your users will need
the same minimum equipment and software required by the
FileMaker Developer application (see the
Installation and New
Features Guide for FileMaker
Pro and FileMaker Developer). In
addition, your users will need instructions for installing and starting
your solution, and information about how to recover damaged files.