OLEDB library for VFP (file #10002) contains simple OLEDB provider, which provides direct access to the internal VFP cursors through ADO recordsets:

loUtils = CreateObject("OleDbFox.Utils")
oRecordSet = CreateObject("ADODB.Recordset")

lcConnString = "Provider=MSDAOSP;Data Source=OleDbFox.DSObject;"
oRecordSet.Open("Customer", lcConnString)

First parameter in the Open() method is alias of cursor. After opening you can pass created recordset to the Crystal Reports.
You can also use CursorToRs methods in this library or VFPCOM utility.


>Jut got your Developer's Guide and was thrilled to be able to preview a report in just a few minutes. Then the depression set in. I have been trying on an off for more than a year to integrate existing reports into our VFP app with little success. What I really want to do is use VFP to prompt for and handle the user inputs for reporting parameters, select the data and then just point the report at the resulting cursor. Crystal has a bad habit of locking tables just when you don't want them locked so if I do the SQL work before the report is called I can control this behavoir. And I can build a much better front end for the users to pick and choose from.
>
>So how do I build a report and then change the data source to a cursor? Or do I have to move the result into a dbf and then use that? Can I pass a cursor name as a datasource to a report from the active-x tool? Did not see any method for that. Or am I just taking the wrong approach all together?
>
>Thanks