VFP 6.0 SP4. I will try your suggestions and see if they help. Thanks.

>I just encountered that it workd in command window and does nto works in trace window. Does it works in run-time? Which VFP version you use? I remember that VFP5 had problems with SQL statements and other commands that have more than 1 line separated by ';', when debugging them in trace window. Sometimes it hangs up VFP for 1 minute, sometimes causes crash.
>
> In addition, you use 'INLIST' and 'EMPTY' functions for query that slow it down. IMHO '=' and 'IN' will be more quick in query like following:
>SELECT * ;
> FROM AuthMst ;
> WHERE (FaxPCPDte ={} OR FaxPrvDte={} OR FaxFacDte={}) AND ;
> AuthStatus IN ('APR','MOD','TRK','DNY','CAN') ;
> INTO CURSOR cRTmp NOFILTER
>
>(I assumed that FaxPCPDte, FaxPrvDte and FaxFacDte are date fields.)
>
> Finally, somewhere I read recomendation to place space before ';' always, I see you not followed this rule in your query in line 4.
>
> Thats all I can tell about this query.
>
>>The SQL Statement is:
>>
>>SELECT * ;
>> FROM AuthMst ;
>> WHERE (EMPTY(FaxPCPDte) OR EMPTY(FaxPrvDte) OR EMPTY(FaxFacDte)) AND ;
>> INLIST(AuthStatus,'APR','MOD','TRK','DNY','CAN');
>> INTO CURSOR cRTmp NOFILTER
>>
>>Does this shed any more light on it?
>>
>>
>>>What is SQL statement??? This command TOO complex to make any suggestions...
>>>
>>>>Out of the blue (meaning that this code has been running for about one year), I run a routine that gives me a Fatal C0000005 error on a SQL select statement. I have searched the threads and found other instances of this occurring. In the past, if we got one on a view opening, we rebuilt our dbc, packed our data and it seemed to clear it. In this case it hasn't. Anyone got some specific info on this and what cause could be.
>>>>
>>>>BTW, if you execute the select from the command window, no problems. In the debug mode where we set step just ahead of the error, the execution of the subsequent SQL statement bombs it.
>>>>
>>>>Thanks for the info.
>>>>
>>>>Bill