>Tom:
>
>Sorry for the delay - the DoEvents call is needed when you have any type of loop. It allows VFP to handle any window events (clicks, etc.) that have occurred. In some cases, a VFP program executing a loop will show as Not Responding in the WindowsNT task manager, even though it is running. Adding a DoEvents in the loop seems to have resolved it.

I've tried the trick I proposed the other day: while in a tight loop, change the caption of your _screen or top level form to something like "Busy, therefore :", and in the Task Manager it will write "Busy, therefore : [not responding]". Restore to normal caption when you get out.

Didn't try under NT, though.