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
2-16 FileMaker Pro Developer’s Guide
Assigning the extension in the Mac OS
In the Mac OS, the three-character extension becomes the creator code
for the runtime application. The creator code must be unique to ensure
that the Finder in Mac OS can determine which application created each
document. The creator code is stored in both the solution files and the
runtime application.
Because creator codes are four characters, FileMaker Pro Binder inserts
an uppercase
F after the first character. For example, the default
three-character extension “USR” becomes the “UFSR” creator code.
Creator codes are case-sensitive.
Important Creator codes should be registered with Apple Computer to
verify that the creator code you choose is unique. If the creator code is
not unique, solution files might not open with the appropriate runtime
application. You may use the default “USR” three-character extension,
as FileMaker, Inc. has registered the “UFSR” creator code with Apple
Computer, Inc. Contact Apple Developer Support or visit their web site
(http://www.apple.com) to register any other creator codes.
Fourth panel of Binder application (Mac OS)
Select for cross-platform files