"The database driver used by this report is not supported by this product"

Is what I get when trying to assign a webviewercontrol.reportsource to a Crystal report that uses a Fox2x table as it's data source.

Also, when trying to bind the same report by adding:

using CrystalDecisions.CrystalReports.Engine;

override protected void OnInit(EventArgs e)
{
//
// CODEGEN: This call is required by the ASP.NET Web Form Designer.
//
InitializeComponent();
base.OnInit(e);

ReportDocument oReport = new ReportDocument();
oReport.Load("C:\\projects\\tc web\\reports\\tempdist.rpt");
webviewer.ReportSource = oReport;

}

All three lines of code fail because it says the proper namespace is missing for the object type ReportDocument. The documentation in MSDN says that CrystalDecisions.CrystalReports.Engine is the correct namespace to add.

If the Crystal reports .net interop does not support dBase based reports, how am I supposed to use VFP based COM to crunch data for reports that have been historically bound to Fox Pro tables.

Also, the plan was to create report objects in VFP COM and bind them to the webviewer at runtime so I can pass all my usual parameters and cursors as we have done in the past with the Windows form viewer. Is this not possible?