Correct. I want to treat VFP data like ADO. In my n-tier applications,
the GUI's are in VFP, and databases are VFP DBC's, but some of the other
components are VB DLL's.

I envision something like the CURSORTORS method in VFPCOM.DLL, except
that I would want to see it as an extension of the SQL SELECT and COPY
TO Commands:

SELECT *;
FROM MyTable;
WHERE SomeCondition;
INTO RECORDSET oRecordSet

and

COPY NEXT 10 TO RECORDSET oRecordSet



If these new recordsets really were ADO
recordsets, then you could do something like:

** In my VFP app, get the records I want
SELECT *;
  FROM MyTable;
  WHERE SomeCondition;
  INTO RECORDSET oRecordSet


IF _TALLY > 0

  ** I got some records, so pass each record to my VB DLL 
  ** for processing

  oVbDll = CREATEOBJECT("MyVbDll.SomeClass")

  oRecordSet.MoveFirst()
  DO WHILE NOT oRecordSet.Eof()
  
    oVbDll.Process(oRecordSet) && The key here is the ability to pass VFP data as a param

    oRecordSet.MoveNext()

  ENDDO

ENDIF