User manual

8-8 FileMaker Pro User’s Guide
2. Determine the database files and the data they will include, and
decide which fields will contain common data among the files. Write
the names of the files and fields on paper.
Each file has only one subject, and all fields in a file describe only
that subject. Based on a file’s subject, you can see where it makes
sense to store the data and where to use data from a related file.
For example, a Route file might have fields for a route identification
number, the departure city, and the destination city. A Trip file might
have fields for a trip identification number and trip name.
3. Determine the match field or fields for each file, and circle
each one.
Each relationship uses one match field in the master file and one
match field in the related file. Match fields are also used to determine
whether a new record should be added to the file. In an efficient
database system, this field often (but not always) contains a value
unique to each record.
For example, in the Client file you might want to assign each client a
unique, identifying number. You wouldn’t enter a client identification
number into the file unless you had a new client to add, so the existence
of a client number determines the existence of a record.
4. For each file, decide which fields will store data, and which ones
will use data from other (related) files. In your plan, cross out the
duplicate fields in the master files. These fields will be related fields
in your database.
The fields in each database file should all store a single occurrence of
the subject of the database file. For example, the fields in one record
of the Client file (client identification number, name, address, and
phone number) together store all the information about one client.
- Information to hold?
- Database files?
- Fields?
- Common data?
Client ID
Street
Postal Code
Client Name
City
Trip ID
Client file
Route file
Trip Name
Trip file
Phone
Route ID
Destination
Origin
Trip ID
Route ID
Destination
Trip Name
Origin
Client ID
Street
Postal Code
Client Name
City
Trip ID
Client file
Route file
Trip Name
Trip file
Phone
Route ID
Destination
Origin
Trip ID
Route ID
Destination
Trip Name
Origin