To All,

>Because the user cna see the city combo and it may be showing an invalid city. I prefer that the user sees the city combo respond to their selection in the state combo. I want it to refresh with the proper cities as the user arrows through the states. It makes the whole app seem more responsive. ...
>
>With my approach, as soon as New York is selected as the state the city list would be refreshed to only NY cities and Boston would disappear from the combo.

Thanks to all who have contributed to this topic. It has turned out to be quite interesting.

Here are some thoughts I've had, and I welcome any comment conerning them.

#1. WHEN vs LOST FOCUS
While I agree that performance optimization should not necessarily be the first or primary design consideration, it just makes good common sense to me to put the code where it will run fastest unless there is a complelling reason to do otherwise. The way I design ComboBoxes, is that as soon as the user makes a choice, the focus moves to the next control. In this specific case, after changing the RowSource to the approariate SQL SELECT, I clear the city combobox. Thus, the user would click on a new state, and immediately the city is blank and receives focus. The user would never see "New York" and "Boston" at the same time.

#2. WHAT'S WRONG WITH LOST FOCUS
There seems to be some sort of background reluctance to use Lost Focus. I don't see any problems with this. If you know of some, please point them out. If anyone thinks this is not a good use of Lost Focus, I'd appreicate any comments on what Lost Focus is best used for.

Thanks to all,
jmu