>Kile,
>
>>That was how I thought Valid() worked, but I couldn't get it to do anything for me in my ComboBox. I read somewhere here on the UT (or maybe it was in the Hacker's Guide...) that Valid() didn't work normally for Combo/ListBoxes. This is why I tried (and failed!) to solve my problem using the InteractiveChange/LostFocus/SetFocus methods.
>
>The difference for Valid is that for a textbox, Valid fires everytime you try to leave the control. For lists and combos it only fires if the controls value was changed while you were in it.
>
>
>>I had originally thought that for an object, if nothing was entered in the code section of a method, DODEFAULT() was automatic. However, if you entered code, (or even blank spaces), anytime that method was fired it would only do exactly what was in the code section of that method, unless you added an explicit DODEFAULT() in addition to your added code.
>
>It does work that way for your code in a class, but for foxpro native behavior you must explicitly tell foxpro to NOT do its native behavior.

This explains many of the problems I was having.

Thanks Jim!