Here is my understanding / method so far:
>The way I do it is as follows:
>1) write SP for data
----> Yes
>2) Generate XML dataset from SP
----> Generate the dataset under app_code (xsd and xss
>3) Create report.
----> Yes ...
>4) Set dataset to report for design purposes.
----> Yes ...
>5) Tweak report layout.
----> Yes ...
>---
>6) Open report requesting interface.
----> Not sure what you mean here ...
>7) Add code for running SP and getting dataset back
----> Done in the dataset project (
.dataset) and the application code to use it.
>8) I now bind the report object from above to the DATASET I just pulled.
----> Here is where I don't know the code to bind the reportviewer and / or objectdatasource ...
>9) Report is now rendered.
>
>It seems that your asking the report to do something with the params and pass them back to the backend? Why ???
----> I can see where the report does not need a parameter if the code to run the SP receives it. I am just beginning to understand this. At first, the report was bound to the app_code dataset since I could not access the .dataset so I figured the report's parameter should get attached the the dataset linked during design. I much prefer controlling all in code where possible ...
>
>Is this easier?
----> Not necessarily. I have had to try the wizards and code oriented methods to understand the process. I was unable to find anything definitive on the web or in the two or three books on vs 2005 and vb.net at my disposal. No one seems to use or care or at least talk much about reportviewer and sql server 2000.
Charles Richard
