This is a classic one-to-many relationship. The "contacts" would need to be
in a new table and they would need to be related to the customer table.
This issue is addressed in this newsgroup all the time.
Rick B
> Hi,
>
[quoted text clipped - 11 lines]
>
> Navin
>Hi,
>
[quoted text clipped - 7 lines]
>better in that case to have each customer his own db and a master meta db to
>control each one's settings. Any ideas or thoughts is appreciated.
"Fields are expensive; records are cheap".
Adding new fields for new contacts is not correct relational database
design! You should have two tables in a one to many relationship,
Customers to Contacts. Each contact is a new record, not a new field.
If you mean that the nature of the information stored for a contact is
different - i.e. one customer wants to store the contact's eye color
and shoe size, and the other customer doesn't - then you've got a
different problem, but that's not obvious from what you post. Is that
the case?
John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps
nvishnu - 08 Dec 2004 18:37 GMT
Yes thats exactly is the case.
> >Hi,
> >
[quoted text clipped - 24 lines]
> Tuesday 11am EDT - Thursday 3:30pm EDT
> http://community.compuserve.com/msdevapps