Hi,
We're using Crystal Reports for .Net 2.0 (Visual Studio 2005).
We have a .Net 2.0 WinForms application with ~46 embedded Crystal Reports that were designed against an Oracle development database using Oracle's OLEDB driver. We are trying to negate the need for the client installations to have Oracle's OLEDB driver installed by taking the SQL from the reports and pre-fetching it, then asking the Crystal Report to use this pre-fetched data instead.
I can get the SQL query out of the Crystal Report at design time, fetch the data it into a DataSet at runtime, call the Report.SetDataSource() method with the DataSet, but then when I assign the Report to the Crystal Report Viewer, it insists on grabbing the data for itself using the OLEDB connection it was designed with.
Is this possible? If so, how? If not, any suggestions for an alternative approach would be greatly appreciated - ideally one that doesn't involve any or too much re-configuration of the existing reports (i.e. a runtime modification would be best!)
Many thanks for any help you can provide,
Andrew :o)
--
Andrew Freemantle, U.K.