>Hello,
>
>We have a serious problem with VFP and the way it handles mouse clicks from a text field.
>
>Lets say we have a field called txtNAME and on the lostfocus event we have a LOT of code which fires when we leave. If the user mouse clicks on another button (let's say called btnHITME), then the first mouse click is not picked up, it seems to be lost. We then have to click on it again for the button to work.
>
>It would appear that when we click btnHITME the txtNAME field realizes we have then lostfocus, but it does not remember that we have a click on btnHITME.
>
>It is all very weird, and only happens when we run code form the setfocus, every control we move to (MOUSEY WISE) from there requires a double click.

A couple of comments in addition to Erik's - you say you have code in Setfocus? That may be causing trouble in the event sequence, you might want to move it to the Gotfocus of the moved-to control...

Also, if the problem is caused by user clicking before lostfocus code is completed, you might want to at least put _screen.mousepointer = 11 (hourglass) in the meantime...

It might help to put a NoDefault at the beginning of the lostfocus, besides a Dodefault at the end of the code...

And one other comment, there's a problem with Lostfocus and mouse clicks if there's a WAIT WINDOW in the lostfocus...