linking fields within the table 1

[NewDBGuy]

I am new to databasing and trying to build basically an asset DB. what I am trying to accomplish is connecting 3 fields that if field one is *.....the field 2 gives you a drop down menu of *, *.

Field #1
Manufacturer
DELL

Field #2
Model
Latitude

Field #3
Model Number
D820

What I would like to do is if field one is a dell (drop down menu has IBM HP SUN...) Then Field two will only show Dell models, and then field three will only show model numbers relevant to that model. I know it should be possible within the table itself I am just not sure how to set it up or google the correct terminology. Thanks for any help or suggestions you can give.

Thanks,
the rookie

 

[Remou]

Try this faq702-4289.

A search for cascading combo may turn up more information.

 

[NewDBGuy]

Remou,

Thank you for the help and quick response, however I only have a single table and did a drop down list within the row source. Would this change the answer as far as the if then else statement? I thought that may be the answer so at least I was on the right track. Any further assistance would be greatly appreciated.

Thanks,
the rookie

 

[Remou]

It sounds as if you have lookup fields, this is not recommended:

http://www.mvps.org/access/lookupfields.htm

 

[NewDBGuy]

I am doing lookup fields....basically because the users are putting in the data, and to control the data accuracy...there are over 500 users inputting data into it so data integrity is an absolute nightmare. Is it more beneficial to make a separate table for those fields instead?

 

[Remou]

Yes, it is much preferrable.

 

[NewDBGuy]

Thank you so much for your help....I have to start over but I would much rather do it right the first time......than to find out it won't work once i start building queries. I really appreciate the help.

Thanks,
the Rookie

 

[lespaul]

you are also going to want to read the fundamentals document linked below to help you get your tables set up correctly...

Leslie

Essential for database developers:
The Fundamentals of Relational Database Design
Understanding SQL Joins

 

[BobRodes]

<I would much rather do it right the first time
You're to be commended for that.

I second lespaul, check especially first normal form. You don't quite have to start over, you can move your data using queries and the like.

Bob