>>Thanks, Rick. That's worth a lot. Would VFP actually lose the events from an ActiveX (or Windows) or would it just queue them up and they hit all at once when it "wakes up"?
>
>I'm not 100% sure actually, but I'm guessing that it won't queue. VFP will be dead in the water while waiting - nothing happens hence there's no way to queue the incoming events. The way events work in Windows is that they're sent and forgotten. If they're not picked up they're gone. Normally VFP's event loop queues them but the event loop won't be running.

If this is true, then it would be impossible to get events in any single threaded process while the process is
doing something.Or, more clear, any single threaded app would lose any events generated while the app is running something else
than the message loop.

So, the events are queued. Basically, from this point of view, there's no difference between sleep(n) and any
other running code. The advantage with sleep() is only that it doesn't take CPU time.

Vlad