If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Best way to design tables for cascading on my form
My company inspects damaged cars for insurance purposes. Up to now,
(relating to this issue) I've had tblDamageArea populate a list box on my form where the user can select the various parts of the car that were damaged. I've had this list include parts for multiple kinds of cars and I'd like to make this list cascade to include only those parts relevant to the car type inspected. I've created a tblVehType to separate Sedan, Coupe, 4DoorTruck, SUV, etc. which populates a cbo on my form where the user will select the type which will then be used as the criteria for cascading the list box. Before that, I created tblParts w/ the Parts but then also had each vehicle type listed out w/ Yes/No boxes where I then selected which parts go with which veh. This is where I'm really needing help. I know this isn't the best way to do it but can't figure out how else at this point to use the tblVehType and connect the related parts to each veh. Many of the parts are the same for all of the vehicles -- for instance the front end parts - they all have bumpers, fenders, hoods, windshields, etc. but the doors (2 vs. 4), quarters (or beds), and rear ends all vary. I imagine that I'll use a query to put them all together for the list box but what is the easiest and best way to set up my tables & dictate which parts go with which vehs? Thanks for your help! Pamela |
Thread Tools | |
Display Modes | |
|
|