Hi, all and thanks.
First, let me say I'm not sure if this is a report problem or a dataset problem...that said, here's what is going on...
I recently upgraded a web site from vwd2005 targeting framework 2.0 to vs2010 targeting framework 3.5 with related update to the web.config. I'm migrating my reports that were built using reportviewer control in vwd2005 to vs2010; in doing so, I accept the prompt to upgrade to the RDLC 2008 format and the upgrade goes ok for the rdlc files (insofar as I can tell). I then go and update my 1st report's aspx page to the new reportviewer control by drag-n-drop (the page is updated with the register assembly call and the web.config's compilation/assemblies and compilation/buildproviders are also updated). I then update the rest of my aspx pages that contain a report. After making the updates to each report's aspx page, I run the report to validate I have a working report.
I use objectdatasource on all the reports except one, which uses a sqldatasource control; about half of the reports take a parameter from the user--like a date range or a person's name. These reports render nothing when the parameter is passed and don't even throw an error. Those that do not take a parameter render just fine
View Complete Post