>Actually the cursor to/from ADO recordset conversion methods of VFPCOM.DLL aren't much faster than my DBF2RS.prg and RS2DBF.prg routines at http://classx.com, mainly because the performance problems in converting ADO recordsets to/from cursors is all the calls needed to the recordset via the IDispatch interface. My utilities also allow you to map the data converted with linked RECNO() info to update the data. I think the biggest feature of VFPCOM.DLL is the .BindEvents().

So, why are the calls through IDispatch? ADO supports dual interface calls
and direct attachment to the CoClasses should provide better performance.

Actually, I'm not sure whether ADO does do dual interface, but I would
presume so. This would drastically change performance of the DLL...

We all know about these problems of course. MSXML has the same problem
for parsing sizable documents.

+++ Rick ---