Synchronised Combo boxes

[matt beamish]

Hello. I am a low level user who doesnt go looking for problems with simple relational databases, but I have a problem now!
I cannot get two synchronised boxes to work properly. I have used various methods that I have found on the MS site - eg http://www.microsoft.com/downloads/...A1-3C4E-4371-81E4-F9347B7A1DD7&displaylang=en
but without success when I try to adapt to my own data. I have not set up synchronised boxes before. Would anyone kindly look at a database if I loaded it up?
Thanks

Matt

 

[rainman89]

post it. someone will have a look

 

[matt beamish]

Thanks. Ive stripped out all but what is relevant.
I want to enter data for sherds of pottery. The pottery is assigned to a "Ware", and then to a "Fabric". So in the form F_Fabrics_test I want the first combo to show distinct wares from T_Wares and the second to show the possible fabrics from T_Fabrics (ie subsets of Wares)
It must be something simple Im doing wrong - maybe with the display of the second combo box?

The combo boxes are unbound, but I want to use them to enter data in the T_Pot_Spec_PR table.

Thanks very much

Matt

 

[rainman89]

Take a look at what i have done. they are called cascading combo boxes. select from the first and the 2nd will change to give u the list of availables

 

[matt beamish]

Thanks Ray. Cascades work well when unbound. How do I then bind these to a table so I can use them for Data entry?

If I bind the form to the T_Pot_Spec_PR table, and then give control sources to the Combo boxes, Ware works correctly, but Fabric is blank.

Thanks again

Matt

 

[matt beamish]

Got it now

Ray,
Ive got it now thanks. The second combo wasnt always updating so I put in a requery clause for the second combo on enter, so that it was always refreshed from the first combo (if that makes sense?).

Thanks very much

Matt

BTW I tend to always put in "ID" autonumber columns for various categories as primary keys, and then set my index fields as "indexed" no duplicates. Although in the main this works very well, when linking together tables, I can get very confused with which field to link on - the Primary key ID or the field itself. I also can get confused further still when in the MS Sample databases, text fields are Captioned as "ID" fields.

 

[rainman89]

glad you got it sorted out. autonumber pks are the way to go. using a FK with meaning is often helpful for referencing