>>The safest bet would be not to spread the code so many places, but a custom property in the form might do the trick
>>

In text2.When
>>IF !Thisform.text1ValidOK
>>  IF !text1.valid()
>>    text1.SetFocus() && or return .f.
>>  ENDIF
>>ENDIF
>>

>
>Sorry, but that makes the hair stand up on the back of my neck. :-) All these events were designed to be fired at certain times, and calling them from each other could make it impossible to debug or maintain later...

Sure, you're the MVP... :-)
Don't get me wrong, I wouldn't use the code above myself, but when here, I try to adjust to others problems. I thought Jim provided pretty useful answer, although it wasn't but a reminder to how things are ment do be done.