Development Guide
Table Of Contents
- Chapter 1 Introducing FileMaker Pro Advanced
- Chapter 2 Creating database solutions
- Chapter 3 Customizing database solutions
- Chapter 4 Debugging and analyzing files
- 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
- Appendix A Feature comparison of the runtime application with FileMaker Pro
- Index
Appendix A
|
Feature comparison of the runtime application with FileMaker Pro 55
Stored registry settings or preferences
Windows registry settings
FileMaker Pro stores its registry settings at
HKEY_CURRENT_USER\Software\FileMaker\FileMaker Pro\.0
FileMaker Pro Advanced stores its registry settings at
HKEY_CURRENT_USER\Software\FileMaker\FileMaker Pro\.0A
The runtime application stores its registry settings at
HKEY_CURRENT_USER\Software\FileMaker\<solution name>\.0
Note The filename extension for the runtime database files is registered at HKEY_CLASSES_ROOT.
Mac OS X preferences
FileMaker Pro stores its preferences in the FileMaker Pro .0 Prefs file inside the FileMaker Preferences
folder.
FileMaker Pro Advanced stores its preferences in the FileMaker Pro .0A Prefs file inside the FileMaker
Preferences folder. The runtime application stores its preferences in the <Solution name> Prefs file inside
the FileMaker Preferences folder.