Help again

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

bob - 14 Jan 2004 21:16 GMT

I have multiple table the parent table holds customer info, the child table
holds out of state info. Due to normalization I am breaking up the tables
because only 25% of my records have out of state info. What I want to do is
to have the primary key from the parent table populate the child table
whenever it is needed. Or perhaps there is a better way of doing this?

Reply to this Message

John Vinson - 14 Jan 2004 22:16 GMT

>I have multiple table the parent table holds customer info, the child table
>holds out of state info. Due to normalization I am breaking up the tables
>because only 25% of my records have out of state info. What I want to do is
>to have the primary key from the parent table populate the child table
>whenever it is needed. Or perhaps there is a better way of doing this?

This is a classic case of "subclassing", and is one of the few
instances where a one-to-one relationship is appropriate.

The easiest way to populate the child table is to use a Form based on
the customer table, with a Subform based on the out of state table,
using the CustomerID as the Primary Key of both tables, and as the
Master/Child Link Field of the subform. New records will inherit the
CustomerID when you enter data into the subform, and linked records
will be displayed together.

John W. Vinson[MVP]
Come for live chats every Tuesday and Thursday
http://go.compuserve.com/msdevapps?loc=us&access=public

Reply to this Message