I am a college professor and am updating my undergraduate database course to use Reporting Services as the reporting tool.ÃÂ The student labs cannot run IIS so I assume that using server-based reports is out and am looking at using local reports and the VB ReportViewer control.
For several reasons (waaayyy too long to list here) I do not wish to use the drag-and-drop datasets that seem to be the core of the ADO.Net 2005 architecture.ÃÂ Instead I prefer to create connections, commands, and datasets in code and to set data binding and manage data updates in code.ÃÂ All command objects map to SQL Server stored procedures.
I need to be able to do the same thing with reporting services local reports but have run into a brick wall in getting the report and/or report viewer to recognize a dataset table created in code.
I would like to do the following (which worked very well in VB 2003 using Crystal Reports):
1. Design report--I am willing to accept the requirement to manually set the Value property of controls since I don't want to set data sources to .xsd files.
2. Instantiate a report object at run time and set it's data source to a dataset table.ÃÂ The underlying query that fills the table would have to contain all columns needed by the report's controls.
3. Set the report object to be the LocalReport for a ReportViewer control.
Can anyone point me to a tutorial or walk-through tha
View Complete Post