The "Not Responding" status in the Windows Task List can definitely be misleading for FoxPro. I don't know exactly how this is determined in the innards of Windows but it's safe to say Windows is not seeing any of the specific types of requests it expects to see, in the time interval it expects to see them. I am surprised it doesn't detect disk I/O requests. IAC, you can easily get this misreported status in the Task List window when FoxPro is performing I/O intensive operations such as reindexing or packing a large DBF.


>Also, the task manager frequently shows "Not Responding" when this is happening (also when appending from another table), however if I leave it alone the append or file close will eventually complete.
>
>Aloha,
>
>James
>>Hi All,
>>
>>I don't know if I'm imagining this, can anyone tell me if I have a valid point...
>>
>>We work heavily with VFP interactivly openning/closing and manipulating the table contents as well as their structures. After switching from VFP 6 to VFP 7 I've noticed that when I close a table it takes a really long time for it to close, sometimes up to 5 minutes on an AMD 1800+ w/256MB SDRAM (WinXP) and not quite as long but still a couple minutes on an AMD 1700+ w/1GB DDR SDRAM (Win2k).
>>
>>I first noticed it on the 1700+ system and initially thought it was an issue of dumping the large amount of RAM to the hard drive. But in the system with only 256MB RAM it takes even longer.
>>
>>Has anyone else noticed this? Is there a solution to increase performance?
>>
>>Aloha,
>>
>>James