>On some slow computers, Select-SQL commands dealing with large files will cause the End Task dialog to display VFP-Not Responding. The hard drive keeps spinning, VFP keeps working and before long the Select-SQL is finished and processing continues.
>
>Does anyone know a reason for this and how to stop it?
>
>This is VFP 5, the Select-SQL reads four tables, each with >10,000 records and the query is fully Rushmore-optimized. The only problem the Not Responding message causes is sometimes users think the app is locked up, they shutdown VFP using End Task and possibly damage a file.
>
>Thanks

"Not Responding" in the Task manager or End-Task dialog does not mean 'crashed' (not responding was perhaps a poor choice of words for windows to use), it only means that the app is busy. All windows apps do this during a computationally intensive process, unless they are specifically designed to respond to windows events in a different thread.

So, there is no way to 'fix' this, because it is not broke. What is broke is the user's perception of what 'Not Responding' means.