>I need to store addesses for different entities. I will create an address table. Anything wrong with creaing a 'ParentID' column and then populating it with the PK of the entity the address belongs to? I know some would say that you shoulds create a CustomerAddresses table and an EmployeeAddresses table, and so on. What do you think?

An Address is an entity, a Customer is an entity and an Employee is an entity. What is a CustomerAddress entity and how is a CustomerAddress "entity" different from an EmployeeAddress entity?