>> I have a Customer table (main office), a Location table (branch
office) and
a Call table ( calls that are being logged). A one to many
relationship exists between the Customer and their Locations. > Each
record in the Call table may optionally have either a Customer or a
Location as Parent. <<
What is the logical difference between a main office and a branch
office? It sounds like there should be a customer table that tells us
all about each customer, and a Locations table that tells us about
each location. If a location happens to be the main office for the
customer, there is a little flag in the Locations table (branch_nbr =
0, or whatever). Therefore, no NULLs have to be used in the data
model.
Received on Thu Dec 20 2001 - 12:38:54 CST
