>>Hi All.
>>
>>I have a client who has been running a VFP application that I installed for him in January 2006. It had been running flawlessly under Windows XP. He recently upgraded his machines to Windows 7 64 bit and now he tells me that he is experiencing this problem on his local machine only where he has VFP installed:
>>
>>I personally get a lot of Windows errors saying Microsoft Visual FoxPro is not responding, and things just shut down. I’ve never lost data or had a data corruption (thank god!). It seems as if the MS Win 7 OS system is pinging VFP to see if it is still alive, and VFP is doing something (and it could be something relatively small), but VFP can’t answer fast enough to the OS, and the OS gives up. This has been coincidental with my current machine.
>
>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.

In the loop (on every 10th record) I'm checking if seconds() has advanced by at least 5 since last time. If it did, doevents force. Save the current seconds() value for the next time.

Works fine.