Dependent ComboBoxes

[HansJ]

I have found lots of material on dependent ComboBoxes and for a LARGE portion of what I am doing, well it works. However...
Working with two different companies, sometimes they will have the same store number and that is where the issue occurs
My first Combo cboGoToRetails Sql states

SELECT Stores.ChainID, Stores.ChainNameFROM Stores
GROUP BY Stores.ChainID, Stores.ChainName
ORDER BY Stores.ChainName;

Me.cboGoToStore.Requery
[/CODE]
Then my second Combo cboGoToStore sql query states

SELECT Stores.StoreNum, Stores.ChainNameFROM Stores
WHERE (((Stores.ChainName)=[Forms]![Hotline]![cboGoToRetail]))
ORDER BY Stores.StoreNum;

As long as the store numbers are not the same the Combo Boxes work as planned. But, let me select a store # that is in Company A as well as Company B, then cboGoToStore will land on the first record source.

What am I missing/doing wrong here?

[orange]

What exactly is a "store number"?
What are you trying to do---in plain English?
What is/are the rowsource(s) of your combobox(es)?

[NightWalker]

Orange,

it looks like he has a list of stores like Home Depot or Wal-mart. Each store has a store number like Home Depot may have 500 stores and each has a number designating it in the home depot main database. The problem I think he is having is Home depot and Walmart may both have a store numbered #123 and he is using cascading CBOs picks Home Depot in first but is getting walmart info in second CBO. I think he is missing the relationship between the store number table and the store table.

My take on it.

[orange]

If that is the case, he must ensure his rowsource in combo 2 gets the store numbers for the company that is the company selected in combo 1.