>Hi,
>
>Today, thanks to William Kuhn, I tried to work with ReportViewer. After reading a brief tutorial I created a simple report and I like it. So far it is much easier than using Crystal Reports. So I will continue working with ReportViewer to learn how to create real reports, not just simple test one.
>
>I wanted to ask if you think that my approach of organizing reports makes sense. I am thinking of creating a separate project for each report. And each report project will have the following:
>
>1. typed dataset(s) report will use
>2. report .rdlc file
>3. form on which ReportViewer control will be dropped
>4. form where user will specify report filter options (these filter options will be passed to the stored procedure to get all or sub-set of records/rows).
>
>Another option is to place datasets in a separate project and reference it in the report project. But I am leaning toward approach where everything related to the report is in the same project.
>
>What do you, people who created real application(s) using ReportViewer, think of the above approach?
>
>TIA.

In our application we were using class library with datasets, class library with BO (each BO is a separate class) and also separate project for forms.