I have been trying to create a DB that will hold info on the windows the we have to offer in our bussiness and then incorperate it with a VB form but i AM Having a **** of a time trying to figure out the design of the DB. So far I have a cluttered mess witch I think could be staightened out with using fewer tabels? the relationship thing has blew my mind.

What I think it should look like:
I need a table named MODELS with field named ModelID , Model Name
a table named GLASS OPTIONS with fields named GlassID , Glass Option
a table named UNITED INCHES with fields named UiID , United Inches
a table named LIST with fields named ListID , List

What I'm haveing trouble comperhending is: Do I really need a table for each record in the model table with the model name,United Inches and List as fields
I know that it should be able to be done using lookup cells(IE: the lookup would point to the other tables) however I don't see how it would work with the VB app.
The Model table would contain 3 records-->Allure,Contour,Enhancement
Glass Option table 3 records-->ProPlus,SolarPro,SeasonPro
United Inches table 4 records-->0-83,84-93,94-101,over 101 add
and List table --->$100,$200,$300
The List price should change according to the record choosenin the tables Model,Model type(ie: single hung,double hung ect.)Glass option, and United Inches
I know the Select statement will retrieve the info I need however I need a good place to start first(good design) witch I haven't been able to come up with so far on my own.
ANY help would be soooo appreciated
Thanks
Crater