>>
>>Ed, I didn't have to use DOEVENTS. The App I tried it with was just sitting at it's main screen (standard READ EVENTS).
>
>Yep; my thought was that a DOEVENTS would force any pending messages to be processed; I've seen VFP sit in tight loops and not process incoming Windows messages (including keystrokes in the VFP context) until the loop finished; just like timer triggers can get backlogged. DOEVENTS force VFP to look at the message queue, so it was worth a shot.

I agree, that would have been my suggestion (if I had thought of it). But since I couldn't reproduce it, I can't tell!