Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / December 2004

Tip: Looking for answers? Try searching our database.

Custom Fields

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
nvishnu - 08 Dec 2004 16:05 GMT
Hi,

I need to design a model where we need to provide custom fields based on the
customer. E.g; customer A may have 10 contact fields while customer B may
have 5 more additional contact fields. This may be enhanced in future to
other tables in the application and also users may be able to add custom
fields from the application. We currently are an ASP and all of clients
reside on same database. Would there be any implication of doing something
like this (custom fields) with having single database. I assume so. Is it
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.

Thanks.

Navin
Rick B - 08 Dec 2004 16:19 GMT
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
John Vinson - 08 Dec 2004 17:49 GMT
>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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.