Cascading combo

[Nonnylizing]

Hey guys
Is it possible to create cascading combo boxes without multiple tables? If yes, then how?
Thanks

 

[theDBguy]

Hi. Cascading combo simply means a dynamic criteria. The criteria doesn't have to come from multiple tables. What are you trying to accomplish?

 

[June7]

Why? What's wrong with having multiple tables? What are you really trying to accomplish?

 

[Nonnylizing]

Hi. Cascading combo simply means a dynamic criteria. The criteria doesn't have to come from multiple tables. What are you trying to accomplish?

I have this database with a form containing multiple cascading combo boxes.... the drop-down of these combo boxes are derived from multiple tables different from the main database table(about 8tables already)
How do I use columns from the main table only to created cascading combo boxes

 

[June7]

If you used main table as source, list can only include values already in records. So for example, if records only have Male as an input then Female would never be available as a choice.

Why would you want to do this? What's wrong with having lookup tables?

 

[Nonnylizing]

If you used main table as source, list can only include values already in records. So for example, if records only have Male as an input then Female would never be available as a choice.

Why would you want to do this? What's wrong with having lookup tables?

Nothing really, just that if something goes wrong with one table, it can really mess a whole lot of things up...

Ok...can I derive my inputs from a single table different from the main database table

 

[theDBguy]

Nothing really, just that if something goes wrong with one table, it can really mess a whole lot of things up...

Ok...can I derive my inputs from a single table different from the main database table

Hi. I'm still at a lost here. But like I said earlier, you can derive your combobox source from any table: single or more. So, I don't really understand the issue. The short answer to your question is a Yes. But if you ask How, I can't tell you without knowing what you're trying to do.

 

[June7]

As an example, vehicle make/model data. Makes table has at least one descriptive field with values Chevrolet, Ford, etc. MakeModels table has at least 2 fields (Make, ModelName). Two comboboxes, one for Makes and one for Models. Models is dependent on Make selected.

Makes table is not essential. These two comboboxes can be based on MakeModels table. Makes combobox would have a RowSource like: SELECT DISTINCT Make FROM MakeModels ORDER BY Make;
However, creating records in MakeModels table would be facilitated by using Makes table as source for a combobox for Make field.

Perhaps you should provide sample data.

 

[Nonnylizing]

Nationality
States
Cities
..all depends on each other
Now I have 3 tables for each of them from where I derived the inputs for my cascading combo boxes

I still have
tblPermitType (taxi, buses, mass transit)
tblRoute
From where I derived the inputs for PermitType and Route cascading combo boxes

Five different tables in all!!!
Can the number of these tables be reduced

 

[June7]

My vehicle schema example still applies. Cities table would have fields for Nationality, State, CityName. Use a form to enter city data. Comboboxes for Nationality and State will use that table's fields as RowSource. State can be dependent on Nationality. Use combobox NotInList event to add values not already in table. Set compound index with all 3 fields to prevent duplicate combinations.

Then use that table as source for dependent comboboxes for tblRoute. The only value that needs to be saved is ID of Cities table.