Access Beginers Question

  • Thread starter Thread starter Greg Jesky
  • Start date Start date
G

Greg Jesky

I think this may be a design question but I hope someone can help.
I have a table with a field called "telephone number" with a value of
telephone numbers.
I need to associate with this field the calling features associated with
each telephone number.
For example:
Telephone "number 1" may have "caller id", "3 way calling" , hunting, voice
mail.
Telephone "number 2" may have no features associated with it.
Telephone number 3 may have 7 features associated with it.
I do not know the best way to organize tables to allow queries, reports,
forms to be used/executed efficiently.
The only table format I can imagine is to make field one telephone number
followed with 10 or 12 features fields(many blank fields).
Thank You,
Greg
 
Greg Jesky said:
I think this may be a design question but I hope someone can help.
I have a table with a field called "telephone number" with a value of
telephone numbers.
I need to associate with this field the calling features associated with
each telephone number.
For example:
Telephone "number 1" may have "caller id", "3 way calling" , hunting,
voice
mail.
Telephone "number 2" may have no features associated with it.
Telephone number 3 may have 7 features associated with it.
I do not know the best way to organize tables to allow queries, reports,
forms to be used/executed efficiently.
The only table format I can imagine is to make field one telephone number
followed with 10 or 12 features fields(many blank fields).
Click to expand...

If you make the phone number a Primary Key in the Phone Number table, you
can then create a second table, Features, with two fields, phone number and
feature. Make the phone number an index but NOT a Primary Key in the
Features table. Now make a one-to many relationship between the two tables
so for each phone number in the Phone Number table, you can have any number
of records in the Features table (one record for each feature assigned to a
particular phone). Any information such as address, owner's name, etc.
would go in the Phone Number table since you don't want it duplicated for
each feature of a phone.

Tom Lake

Tom Lake
 
Back
Top