This should be working

[nichclark]

I have downloaded an example of cascading combo boxes that look at a table that has three fields in it. Each combo box will rely on the value of the previous combo box. I'm able to produce two combo boxes that are cascading but I can't seem to get the third to work.

I hope this makes sense

 

[boblarson]

Well, I'm not surprised it isn't working right, because the table structure is not designed properly.

What are you planning on trying to capture data on? Don't take this personally, but you need to get some reading on Data Normalization BEFORE going any further. If you don't, you are going to find yourself (and your users) suffering down the road.

Check out this link to start with:

http://support.microsoft.com/default.aspx/kb/100139

 

[nichclark]

Thanks for the quick reply, I'm not going to take anything personally and any help I can get it very much appreciated. I'll have a look at the link.

 

[ajetrumpet]

Nich,

I agree with Bob about the normalization issue. I'm not sure why you have so many words in your cell values. There has to be a way to break those apart. It looks more like an essay rather than a recordset.

Anyway, the reason your 3rd box wasn't working was because you did not include "cbstate" in the rowsource for the "cbcounty" control. I added that and put it in the zip file for you to look at...

 

[boblarson]

Nich,

I agree with Bob about the normalization issue. I'm not sure why you have so many words in your cell values. There has to be a way to break those apart. It looks more like an essay rather than a recordset.

Anyway, the reason your 3rd box wasn't working was because you did not include "cbstate" in the rowsource for the "cbcounty" control. I added that and put it in the zip file for you to look at...

And let me elaborate further on what I was going for. You should not be storing the same text over and over again. If you find yourself doing this you need to have a separate table where you have an ID field and then the text and you then store the ID in the main table which you can then tie back together in a query for display purposes. But, if you ever needed to change the particular text, you wouldn't need to touch hundreds, or thousands, of records. By using the ID field, you would only need to fix the text in ONE place.

 

[nichclark]

I see what your saying, by me creating seperate tables I won't need to repeat words over and over again which is going to reduce the size of my database.

 

[boblarson]

I see what your saying, by me creating seperate tables I won't need to repeat words over and over again which is going to reduce the size of my database.

Yes, that is PART of the normalization process.

 

[nichclark]

Thanks so much for your help, if you could have a look at the following and try and point my in the right direction I would be very grateful. I'm learning alot on this forum.