I have reports running fine that are using an OLEDB connection to a VFP database. These are multiple table reports and the tables are deleted and recreated in the database each time a new report is run. The database container basically acts as a repository for temporary tables. In the desktop version we assigned temporary fox2x tables to the reportengine which obviously won't work in .NET.
The obvious issue here is overlapping web hits running the same report using the same database and tables. I want to create a new database and the necessary tables for each report that is associated to a SessionID from ASP.NET. That's fine and can be done with my VFP Interop. The difficulty I'm having is assigning the new database as a datasource to the report. I have tried this:
ReportDocument oRpt = new ReportDocument();
oRpt.SetDatabaseLogon("","","OLEDB",@"c:\webdata\webreports.dbc"); <-- This fails
oRpt.Load(@"c:\webreports\myreport.rpt");
CrystalReportViewer1.ReportSource = oRpt;
The Error is Invalid File Path but I don't believe that is the real problem since the path is correct.
Does anyone have an example of the correct syntax for SetDataBaseLogon where the a username and password are not required and the connection needs to be an OLEDB connection to a VFP database?
Eric Kleeman - EDS Consulting Services
MCP Visual FoxPro
MCSD C#.NET
Hua Hin Thailand
Los Angeles California