Database Reference
In-Depth Information
lets you choose any file type, including those that FileMaker doesn't support, you'll al-
most always change it (see
Appendix C
for a complete list of supported file formats).
▪
Storage options
gives you three choices: “Let user choose,” Reference, or Insert.
▪
Display
lets you control what's displayed in the field after a file is inserted. The choices
are “Icon with filename” and “Content of file (when possible).” Image files with suppor-
ted formats will show their content. You'll see the first page of a PDF file, a frame from a
video file, or a thumbnail version of supported image files. All other files show an icon
with the filename. Most often you'll choose “Content of the file” for interactive contain-
ers and fields in which you'll store images. If a container file will store other file formats
(like word processing documents or spreadsheets), then choose “Icon with filename.”
▪
Compression
lets you choose whether a file is compressed before it's embedded into a
container field or moved to the base directory for the field's external storage. The choices
are “Never compress,” “Let user choose,” and “Compress when possible.” Some files
can't be compressed. For example, if a file is already compressed, it can't be compressed
further. Note that this option is grayed out if you've selected Reference in the “Storage
options” section.
Figure 12-5. When you choose one of the predefined options, FileMaker puts the proper data in the
Name and Extensions fields. Here you see the settings for inserting image files. But you can edit the
definition if you need to. If you don't want to allow bitmap files in your database, just select the
“*.bmp;” part of the extensions data and then delete it.
Creating a Field Script
The Customer table in the sample database has a Notes field that's used to hold any informa-
tion you think is important about the customer. Unfortunately, you soon realize this field is a
little
too
unorganized. You have no idea if the note that says, “Customer already paid” is
from last Tuesday or last year. You need a consistent way to keep track of
who
left a note,
and
when
. You decide everybody should record this information along with any notes. To
make things even easier, you want to be sure people add
new
notes
above
older notes. Thus,
when a customer record has been around for a while, the Notes field looks something like
this:
