Is there yet a standardized way of efficiently converting a VFP cursor to an ADO recordset? I've been looking over VFP 8 beta and it seems that the cursor adapter class in one-way (inbound). You can go from ADO to VFP cursor but not the other way. There has also been some talk about solving this relating to the VFP ole db provider... i.e., by putting a wrapper around the VFP ole db provider (I've seen some posts in the downloads forum), but I'm not sure how well that works.

What I really am wanting to do is create a VFP cursor within an MTDLL that is called by an Active Server Page application, convert the cursor to an ADO recordset, and pass the recordset reference back to the ASP app. So far, the only way I've found to do this is the following:
1. Assuming a complex sequence of queries, have the final step of data retrieval in the MTDLL produce a VFP table rather than a cursor.
2. Do an ADO "select *" from the table into an ADO recordset.
3. Return the recordset object reference to the ASP app.

Is there a more efficient way?