>Hello Floyd.
>
>Neither the lower level form nor the code that invokes it are in violation of the valid() event constraints in the higher level form. That is, philosophically speaking ;)
>
>I hate to contradict you here, but you know I am going to < s >. Clearly, if there is a pending valid anywhere in the call stack, there are some unresolved issues about whether or not some control somewhere was allowed to lose focus.

Marcia;

I have to agree with you. One rule we followed was to not use When or Valid to make calls involving SetFocus. I was consulting at a company, which had just begun to use VFP 5.0 and converted its application to that version from Windows 2.6a. The VFP application had been in use for almost 6 months at many customer sites when suddenly it “blew up”. It seemed someone had a call from a Valid to SetFocus and it had worked all that time. When it blew up it refused to work again. The offending line of code was removed, replaced and all was well. Even with an SQA department this was not caught. There is nothing worse than having a customer tell you “we found a problem”!

Events like the above are of concern, as you should never violate a rule. The fact that VFP allowed this rule to be violated is something I will never forget! Such violations will come back to bite you. :)

Tom