You can have the same address for more than one person and some of them could be employee, other customers, etc.

>A customer table typically is linked to a contacts table as well. For your employees that record may contain the emergency contact person if you want to use the contacts table for two purposes as well.
>
>If you share the address table, you could identify the type of address table record with a code (E for employee C for customer). If the address table also includes the header information, you could link it to the contacts table (if the address table actually contains more information than just the address) for both customers and employees. Not sure by your description if the address table only includes addresses and nothing more.
>
>Or you can have an employee table and a customer table and just link them to the address table and to the contacts table by a key. (My recommendation but add a code in the address table to denote the type of record it came from if you will be doing a LOT of reports based ONLY on geographic location later - and I mean a LOT where you don't want to look at the header record first to determine which records to pull in the address or contacts table)
>