Rex,

>I have an application which uses locations (addresses) for several business object and I am thinking of creating a location business object.
>
>The table structures have been modified moving the address1, address2, city, state, and ZIP fields to the LOCATION table and replacing them with an iLocationId field.>

If parent records can only have a single associated address, what's the rationale for moving the address fields into a separate table?

Regards,