Sympathies, Kim. Normalizing data and knowing what relationships should exist is a real art, butI think you're on the right track. From the above it sounds like one attribute in table A should be identical in table B and should have a one-to-one relationship with its record in BOTH table. So, if phone number is the linked attribute, make sure that each phone number isu nique to its record in both tables. No 1:n or n:1 relationships will work as the linking field. (This makes sense to me, but if it doesn;t make sense to you, feel free to ignore it!)

As for the "boss who wants it all in one place", be very wary of requirements voiced in haste by the ignorant. She may not know what she is saying!!

I would suspect that what she really wants is a front end that can tell her whatever she needs to know and she actually does not care what data is in which tables, as long as she gets the front end she needs. Regards,

A