Hi Viv,

>Sort of off thread, but I'm wondering if that is true. I'd expect a higher priority interupt to occur during the execution of a lower priority one - but not the reverse. Admittedly I'm thinking in terms of hardware interupts here but the same logic would surely need to be present in this scenario. The alternative would surely be chaos <g>. I also don't know which of the above would have the highest priority but I'd bet on the Comm event.
>

Maybe OT, but interesting ;-)

I think you'd be right. Whether VFP uses GetMessage or PeekMessage to process events, both prioritize according to the MSDN Library:

Sent messages
Posted messages
Input (hardware) messages and system internal events
Sent messages (again)
WM_PAINT messages
WM_TIMER messages

I'd say the timer loses. See also: http://support.microsoft.com/default.aspx?scid=kb;en-us;143303