Filemaker Pro 9 (49)

Question 1

1. Most real world problems have LOTS and LOTS of entities, so the second step is to:

Answer 1

figure out which ones matter.

Question 2

2. You might eliminate ITEMS for any one of FOUR MAJOR REASONS:

Answer 2

a. They’re already covered
b. They’re too specific
c. They’re just attributes of another entity.
d. They’re not important enough to track.

Question 3

3. After thinking about each ENTITY on the list, you can:

Answer 3

REMOVE AND POSSIBLY add some new ones. When you’re through with this step, you have a pretty GOOD LIST OF ENTITIES-and TABLES- in your database.

Question 4

4. What do Relationships tell FM?

Answer 4

RELATIONSHIPS TELL FILEMAKER WHICH RECORDS IN TWO TABLES GO TOGETHER.

Question 5

5. Conceptually, RELATIONSHIPS come in three flavors:

Answer 5

a. ONE TO MANY
b. MANY TO MANY
c. ONE TO ONE

Question 6

6. In a ONE TO MANY RELATIONSHIP, one record in one table relates to:

Answer 6

SEVERAL records in the second. One INVOICE RECORD has SEVERAL LINE ITEMS, so it is a ONE TO MANY.

Question 7

7. Similarly, SEVERAL LINE ITEMS BELONG TO ONE INVOICE, so it s a MANY TO ONE RELATIONSHIP. Since RELATIONSHIPS WORK BOTH WAYS:

Answer 7

a ONE TO MANY IS ALWAYS A MANY TO ONE.

Question 8

8. Explain a MANY TO MANY RELATIONSHIP

Answer 8

You have a PRODUCTS TABLE and an ORDERS TABLE. They have a MANY TO MANY RELATIONSHIP: a PERSON ORDERS MULTIPLE PRODUCTS, AND EACH PRODUCT CAN BE ORDERED MANY TIMES (by different people?)

Question 9

9. Explain a ONE TO ONE RELATIONSHIP

Answer 9

If your database holds pictures of each item you sell, you could create a PICTURES TABLE, and each PRODUCT RECORD on the PRODUCT TABLE is related to exactly ONE PICTURE RECORD in the PICTURE TABLE.