Now you lost me.

In the Crystal Database Expert I connected to SQL and selected the stored procedure and brought the SP into the report. I then dragged fields from the Field Explorer into the report. There was no DataSet involved. I have always done it this way.

Also, reportObj.SetDataSource expects a DataSet, not a string, so how does the table name come into play?


Kevin, first, what you described is how you might build it at design time. However, that winds up populating an internal database table object collection in CR.

At runtime, if you want to provide actual data (dynamically) for the the table definitions you initially created, you use SetDataSource.

However, take a look at the code I sent. When you call SetDataSource, you're doing it for every table object in your initial report (even if your initial report only contained one table). Yes, it expects a table name...but how you refer to it is by using the table name of the ado.net datatable object.