Developer’s Guide

Table Of Contents
4-8 Developer’s Guide
Assigning a three-character filename extension
The three-character filename extension associates all of the solution
files with the FileMaker Pro runtime application. If a user has more
than one runtime database solution on a machine, the filename
extension together with the binding key will ensure that the correct
runtime application is started when a solution file is double-clicked.
Use an extension that is unique to your users’ computer systems.
Assigning the extension for Windows solutions
The three-character extension registers your runtime application
with the Windows operating system. The extension is used by
Windows to determine which application starts when you double-
click a solution file. The Developer Tool appends the extension to all
database filenames in the runtime database solution during the
binding process.
Assigning the extension for Mac OS solutions
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 Mac OS Finder can determine which application
created each document. The creator code is stored in the solution
files and in the runtime application.
Because creator codes are four characters, the Developer Tool 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.
Note 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 USR three-character extension
because FileMaker, Inc. has registered the UFSR creator code with
Apple Computer, Inc. Contact Apple Developer Support or visit
their web site at www.apple.com to register any other creator codes.
Conflicts with non-unique filename extensions
If the three-character extension is not unique, it might cause registry
(Windows) or desktop (Mac OS) conflicts. For example, if you use
the .fp5 extension for your runtime database solution and your users
have FileMaker Pro installed on their hard disks, all of their
FileMaker Pro document icons (and the application icon in the
Mac OS) will change to the runtime icons. Additionally,
FileMaker Pro documents will no longer automatically open the
FileMaker Pro application.
Windows To restore the document icons to the original
FileMaker Pro document icon:
1. Discard the runtime application.
2. Open a document in the FileMaker Pro application, then close it
and exit the application.
3. Restart your computer.
Mac OS To restore the document and application icons to the original
FileMaker Pro icon:
1. Discard the runtime application.
2. Rebuild the desktop file: Hold down Option + 3 and choose
Special > Restart. Continue holding down the keys while the
computer is restarting. Then, when it displays an alert dialog box,
click OK to rebuild the desktop.
The .pec filename extension associates
the files with the runtime application