Development Guide
Table Of Contents
- Chapter 1 Getting started
- Chapter 2 Customizing database solutions
- Chapter 3 Customizing menus
- Chapter 4 Creating custom layout themes
- Chapter 5 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
- Chapter 6 Debugging, analyzing, and optimizing files
- Chapter 7 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 8 Distributing runtime database solutions
- Appendix A Feature comparison of the runtime application with FileMaker Pro
- Index
Chapter 8
|
Distributing runtime database solutions 81
Including printed documentation
In addition to an online Help system, you should include printed
documentation that explains how to install your database solution and
briefly how to use it in case users are not able to open your solution
files.
Other items appropriate for printed documentation include:
1 how to install your bundled solution
1 how to install custom files
1 how to upgrade to new solution files
1 how to use your Help system
1 how to start the database solution (see “Starting runtime database
solutions” on page 78)
1 what to do in case of a damaged file (see “Recovering damaged
files” on page 78)
1 how to reach you for technical support
You might also want to include the following recommendations:
1 Tell your users not to rename any solution files (except the runtime
application), or they may be unable to run your solution.
1 Recommend that users back up their data regularly. You might
want to automate some of the process by including scripts that save
copies of the solution files. For more information, see Help.
Important In the event that your runtime database solution files
become damaged, make sure users have access to your technical
support email address or telephone number in your printed
documentation or in a text file. If a database file is damaged, they may
not be able to access the About layout in your solution to find out how
to contact you.
A kiosk example containing a single Help layout
A runtime solution example with a separate Help window