Linking list boxes?

[99scollings]

Perhaps I'm not using Google very well, but can't find anything of any use to me concerning this.

OK, so I'm working on a database for ICT coursework (therefore know diddly squat about them lol). 2 tables: CarMake(Registration, Make, Type) and Model(Make, Model). Make obviously links to Make in the first table. What I would like to do, is when someone selects a car make, a [small] list of models is displayed corresponding to that model. Hope that makes sense. I rather wouldn't delve into VB code if I could help it, but will if I have to. I would be very grateful if anyone could help! Many thanks :),

Soraya.

[NeoPa]

I would suggest that you go into Access and create the tables as described.
Link the tables in Relationships.
Create a query returning results from linked tables (INNER JOIN or Type 1 link).
Create a form based on the query, using the Form wizard.
If this doesn't give someone studying ICT what they need then we can help further I'm sure.

It's a more sophisticated way of doing a simple form with an unbound combo listing the Makes.
Let us know if that's the approach you would prefer.

[MMcCarthy]

Perhaps I'm not using Google very well, but can't find anything of any use to me concerning this.

OK, so I'm working on a database for ICT coursework (therefore know diddly squat about them lol). 2 tables: CarMake(Registration, Make, Type) and Model(Make, Model). Make obviously links to Make in the first table. What I would like to do, is when someone selects a car make, a [small] list of models is displayed corresponding to that model. Hope that makes sense. I rather wouldn't delve into VB code if I could help it, but will if I have to. I would be very grateful if anyone could help! Many thanks :),

Soraya.

If Make is not a unique value then it shouldn't be the primary key of the Model table. In fact you shouldn't have been able to make it the primary key. It would make more sense for Make and Model together to make up the primary key.