Cascading Combo Boxes

[Len Boorman]

If all gropus are in the single table then why does qry_Update appear

SELECT DISTINCT [List:Group].group, FROM [List:Group Classification] UNION Select null, "<All>" as Bogus FROM [Vendor Classification]
ORDER BY [Vendor Classification].Classification;

Problem is that we actually need two columns in the first bit so that the UNION bit which will have Null and <All> as values will match.

Otherwise you will have eithet <All> as a value in the combo box or null which may be acceptable if you put a note alongside to say select "blank" for all.

I was presupposing that you would have an identifier as PK and a description in the combo then you have Null and <All> values fitting nicely.

Len

 

[zappa007]

hey Len,

you've given me plenty of insight...as a matter of fact, i think it sparked the answer...

I will play around with it over the next day and let you know how I make out...

again, i really appreciate the time, patience, and wisdom..

ed

 

[Len Boorman]

...as a matter of fact, i think it sparked the answer...

frequently the answer finally comes from the questioner. That means they have learnt a great deal and understand why it did not work before and why it now works.

That's learning.

L

 

[zappa007]

Hey Len,

Wanted to give you a quick status....

Like I said, I inherited the database and the flaws in its design. I had to address those before I could get these combo boxes working properly. Once I made those changes, I was able to successing implement the cascading the way I wanted.

When you had mentioned PK, I realized that if I made a few adjustments in several tables, the Union would work...and it did....Once I got that, the rest fell into place.

Again, I appreciate all your help.

ed

 

[Len Boorman]

Hey

Isn't learning wonderful

You now understand cascading combos, and <All> and a few other bits beside probably.

Glad I was able to point you in the right direction and well done is resolving you problem

Thanks for the feedback

Len