Winla
Jun 11th, 2007, 06:27 PM
I couldn't figured out this:
My system: VS C# 2005, SQL server 2000.
When I created a crystal report using a stored procedure with parameters as report datasource through report wizard, I had this problem:
If I chose OLE DB (ADO) connection, I could see it automatically set the parameters in the parameter fields in CR, which means everything is fine!
If I set the stored procedure as ADO.NET Dataset and use it as datasource, there is no pupup for parameters during report creation wizard. When I checked tableadapter for the stored procedure in the dataset, I can see the GetData(@mypara) works fine
I would prefer ADO.NET approach. but I couldn't figure out why it didn't work out.
Search around didn't find anything . Any clue?
thanks
I figured out why. CR treats the ADO.NET Dataset objects different from OLE DB Datasource. You wouldn't see real data unless you push the data into the dataset first. So there are no parameters popup. It is OK
My system: VS C# 2005, SQL server 2000.
When I created a crystal report using a stored procedure with parameters as report datasource through report wizard, I had this problem:
If I chose OLE DB (ADO) connection, I could see it automatically set the parameters in the parameter fields in CR, which means everything is fine!
If I set the stored procedure as ADO.NET Dataset and use it as datasource, there is no pupup for parameters during report creation wizard. When I checked tableadapter for the stored procedure in the dataset, I can see the GetData(@mypara) works fine
I would prefer ADO.NET approach. but I couldn't figure out why it didn't work out.
Search around didn't find anything . Any clue?
thanks
I figured out why. CR treats the ADO.NET Dataset objects different from OLE DB Datasource. You wouldn't see real data unless you push the data into the dataset first. So there are no parameters popup. It is OK