FileMaker Pro 4.1 Mac User's Guide

10-8 FileMaker Pro User’s Guide
Lookups and relational databases: a comparison
?
Whether you define a lookup or create a relational database depends on
how you plan to use the data from another file. Use the following
information to help you decide.
Use lookups to:
1 Copy data from a different file (or the current file) and keep it as
copied. For example, use a lookup to copy values from a Current
Price field to a Price field in an invoice file. Even if the price in the
original file changes, the value in the invoice file stays the same.
1 Maintain a file that already contains lookups, when you don’t want to
change the files to a relational database.
Use a relational database to:
1 See and work with data in its most up-to-date state. This is important
when you need current data, like values in a Days Past Due field from
a related file.
1 Set up and manage data efficiently and with flexibility. Instead of
creating many database files that together store multiple occurrences
of data, you store single occurrences of values in smaller files. You
can then work with the data in many ways. You make any changes to
data in only one place, which promotes data accuracy.
1 Save disk space, because data is stored in only one place.
Note A complex set of lookups or a complex relational database may
require an administrator who understands the design and how to
maintain it. The administrator might also train others to use the database.
Choose FileMaker Help Index from the or Help menu, and then type:
E lookups, overview
E relational databases