>I came across this code, which goes back to VFP3, and do not understand how it works. If I did I would continue using it. I am planning on using a transaction numbering scheme to id unique records in the children.
>
>The Query:
>SELECT 'Escrow' AS Account,P.Prem_Cnty AS County, P.Fileno,D3.*, ;
>'3' AS DisbFile,Recno() AS Recno ;
>FROM Parent P,Disburs3 D3 ;
>WHERE P.Titleno=D3.Titleno.and. ;
>Between(D3.ToBeDisb,gdBeginDate,gdEndDate) .and. ;
>P.Prem_Cnty=gcCounty ;
>INTO DBF (gcLocPath + "\dbfTemp") ;
>ORDER BY 2,1,3
>
>Parent.dbf is the parent, Disburs3 is a child.
>
>What I do not understand is why Recno() returns the matching record no. in Disburs3? why not from Parent?
>
>I tried Recno("Disburs3") and got the one record no. the cursor was on when DbfTemp was written.
>
>Any clues would be appreiated.
>Carol

RECNO() is unreliable when used in a multi-table SELECT. This is documented in the help file. This occurs because VFP does a USE AGAIN on the tables, which creates a different alias.