I removed the whereclause from the subquery and everything is fine. We've had other problems with reserved words as field names and aliasing them did fix the problem. Never let a DOS Clipper programmer do your data design.

I started cutting the subquery down, one phrase of where clause at a time until I got the sub query to work. I even removed them in every possible order (ther were only 2). The subquery would execute when the where clause rmoved.





>I would suggest aliasing your tables. If you use table aliases you can avoid the reserved word problem. Also I think that the distinction between the number field in the main query and the number field in the subquery is unclear.
>By aliasing the incoming and receipts tables you can reference the fields by table.
>
>>This is absolutely not the case. I use WHERE clauses in subqueries all the time. I'm betting the use of number,date and type as field names and as the ORDER BY criterion is what's is causing the trouble. These are all reserved words in VFP.
>>
>>>Okay, being stupid, appears that a where clause is invalid in a subquery.
>>>
>>>
>>>
>>>>In VFP 5.0 I seem to be having a problem with a subquery. I can run the subquery stand alone and it works fine. Please someone tell me what I'm not seeing.
>>>>
>>>>****
>>>>
>>>>SELECT uniqueid,number,date,type,sn,payee1,document from incoming ;
>>>> where BETWEEN(date,Thisform.sdate.value,thisform.edate.value) ;
>>>> and number NOT IN (Select number from receipts ;
>>>> where BETWEEN(letterdate,Thisform.sdate.value,thisform.edate.value) ;
>>>> and lettertype = [I]) ;
>>>> order by number ;
>>>> into cursor curLetter NOFILTER NOCONSOLE
>>>>
>>>>*****
>>>>
>>>>Ideas?