>Hi Mark ----
>
>Maybe an active Timer that fires off some sort of message every .n seconds?

VFP is not too well-behaved about responding to events during a single, compute-intensive operation. My experience is that for some commands at least, VFP does not respond to standard Windows Messages until the next statement is started; with VFP timers at least, the timer events fire (and they'll back up in a queue) bu VFP doesn't repsond to them until the current atomic line of code completes. By atomic, I mean a single line of code; I haven't tried to find out if a SQL Select with embedded macro expansion will respond to times each time that macro expansion takes place. A SQL select may not be an atomic line of code if, for example, there's a UDF() or VFP object method reference in the SQL Select statement.

VFP looks like a runaway freight train at times...even though eventually the engineer does wake up most of the time.

>
>>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