>Hi Fred,
>
>>No, I have not tried your test. The "processing" I was referring to was SQLs to build a cursor for a report and running the report. When I used to return from the report, if the user had pressed the button while this was going on, the report would run again. DOEVENTS stopped that for me.
>
>One explaination I could think of is: VFP does not allow recursive firing of an event. When you are in an event, the same event won't fire again. With DOEVENTS you force VFP to process events right now, but it can't fire the Click event, because you are executing it. Since now the event is processed, it won't be saved as usual and therefore won't be executed after the report.
>
>Christof

Christof, that sounds like a rational explanation for the behavior I'm seeing. I'd much rather know there's a reason why something happens the way it does then to just take it on faith that that's the way it works. Thanks.