Craig;

Well, you definitely need to be VERY careful with RECNO - I always use the alias name to specify WHICH recno I want. Most folks have forgotten that optional parameter exists.

I found that using a different alias name solves the problem (which acted the same way in VFP6). It must be a reserved word in SQL, 'cause I didn't see it in the VFP reserved words.

Well, I got it working, anyway. Thanks for the response.

>Off the top of my head, I can't say why it throws that error. However, using RECNO() in a SELECT with multiple tables will return unreliable results.
>
>>Argh!
>>
>>I'm using VFP7. I'm creating a cursor, then trying to use it again in a SELECT:
>>
>>

CREATE CURSOR Attend(Attender C(8))
>>
>>FOR i=1 TO lnVars
>>	INSERT INTO Attend(Attender) VALUES(laAttenders[i])
>>ENDFOR

>>
>>This does indeed create a cursor, with several records - but then:
>>
>>

>>SELECT Attend.*, SchedContribs.UserCode, RECNO('SchedContribs') AS Recordnum ;
>>	FROM Attend ;
>>	OUTER JOIN .\Extranet\SchedContribs ;
>>	ON Attend.Attender=SchedContribs.UserCode ;
>>	WHERE SchedCode=lcSchedCode ;
>>	INTO CURSOR TQuery
>>

>>
>>Reports: "Alias 'ATTEND' is not found." - Even though my data environment clearly shows a workarea with that name (which I can browse). I've tried using DBF('Attend') instead, with the same results.
>>
>>Any ideas?
>>
>>TIA