>>See if he can test with real-time antivirus scanning disabled.
>>
>>If that's not it ISTR Dragan started a thread a little while ago with a similar issue. I think judicious use of DOEVENTS was suggested, I don't know if that was the final solution.
>>
>>This application has run flawlessly since 2006. These problems just started to occur after he upgraded from Windows XP to Windows 7.
>
>Exactly, because the behavior of Windows has changed. It now considers an app which doesn't respond to a roll call unresponsive, which is the same as before. However, it doesn't leave it alone like previous versions of Windowses did, it now renders its window in milky white, and if you try clicking around it, it goes completely white and you get the offer to shut it down. If you leave it alone, it may respond to another roll call, and it may be allowed to refresh.
>
>My situation is pretty much the same - have a conversion prg which I compile and run from within the app, which just reads some outside data source and insert records into the app's tables and tableupdate()s them. Every n records I'd wait window recno()/recc() nowait or some such progress indicator. Well, the wait window is the first thing which stops refreshing, even if the app's window isn't iced. Generally, Windowses now don't want your code to be busy, they want it respond to roll call and be clickable at all times. We don't want no damn batch processing, this isn't a computer, this is a Windows machine...
>
>See my answer to Al, the solution is quite simple.

Thanks Dragan.