>How would you handle a combo-box with Style set to "2 - Dropdown List"? In this case, the Valid fires whenever you pick an item, but doesn't prevent you from leaving the control. I guess there are other ways of designing the interface so this problem isn't run into, but it seems like odd behavior to me regardless.

The valid doesn't apply to drop down lists since, by definition, they can't have invalid values. So, you need to, IMO, rethink what's happening. Either it should be a drop down combo which you validate, or it needs to be a drop down list, which you don't need to validate. What is the situation? You have a drop down list that has a blank entry in the list, but you don't want users to be able to select the blank item?

It would be easier for me if we had a scenario to talk about.

Let's say the drop down lists available classes and a blank item. If the user selects one of the classes, they can then click a button to look at the detail. If they've selected blank, then clicking the button to show the detail shouldn't be active. You could a couple of different things.

In dropdown list's interactivchange, set the enabled property of the button to .F. if the list's value is empty. Otherwise, enable the button.

If, on the other hand, the user should NOT be able to select the blank item, then don't put it in the list at all.

>Also, in your example (as in mine), I guess focus is still in the textbox after using the access key. However, the command button has the dotted line around it as if it had focus, too.

Yes, I agree that's weird.