Hi Jim,

Thanks for the suggestion. I tried using the field position numbers, but I still received the ICE.

Thanks,

TFISHER

>Since you're into trying *anything*, I wonder of using numbers in the ORDER BY might make a difference. I know I've had to resort to that in some cases.
>
>I assume that your output is smallish.
>
>good luck,
>
>JimN
>
>>Hello,
>>
>>Can anyone tell me how to better write the following SELECT:
>>
>>SELECT a.def_id, a.casenumber, a.vlastname, a.vfirstname, a.arrestnum, a.codenum, ;
>>a.arrestdate, a.arresttime, b.lname, b.fname ;
>>FROM defendan a, Person_a b ;
>>WHERE a.arrestnum = b.arrestnum AND a.casenumber = m.case ;
>>ORDER BY lname, fname ;
>>INTO CURSOR lctest
>>
>>This is in a FPW 2.6 application. It works fine on some machines, but creates an ICE on other machines. On some machines, it works fine for a while, then creates an ICE. Once it creates an ICE, I can not get the SQL to work again without getting the ICE.
>>
>>I have traced the problem to the ORDER BY clause. If I remove the ORDER BY, the ICE does not occur.
>>
>>I have tried everything to clear up the ICE. My Config.sys has RESOURCE=OFF as the first line. I have re-created the indexes on the tables. I have deleted the Foxuser files. I have deleted the .tmp files. I have defragged the hard drives. etc. etc. etc.
>>
>>If there is no way to fix the SQL statement to get rid of the ICE, is there an easy way to order the cursor after the SQL has run?