John,

So a DoEvents() call still takes on the order of 250 milliseconds to execute? I haven't ever gotten a chance to test it in the beta. That performance hit just is plain stupid. Typically in Win16 you needed to do a PeekMessage() in a processor hog loop to let other apps get a time slice. Win32 was supposed to be more pre-emptive in it's multitasking. But maybe it's an issue that VFP only has one thread for these calls.

>Okay... DoEvents does seem to work.....sometimes. On a few occasions, processing would hang. At other times, the call to DoEvents had a major performance penalty. Also, I am curious what issues arise when calling a DoEvents in the MTS environment. The more I run the code, the more unstable it gets. So, it does not look like DoEvents is a viable alternative.