Larry, the other message had some errors. Here goes the correct one:

What I do for reporting is to integrate all of them in a single form. Basically, the form has a treeView control with all the reports organized in branches for easy localization.
Almost every report has an associated page in a page frame besides (or below) the treeview control.

The page frame has no tabs, and when you select the report, the corresponding page is activated showing you the 2 or 3 (or 20) controls related to this report. If there are too many pages, you can use delayed instantation.
When the user has selected the report and the options for that report, then he/she can choose from the menus and specify where to send the report: screen, printer, file in several formats, directly to Excel, or email (basically a report to PDF or HTML, and then this PDF is attached to a message or the HTML is inserted into it).

This way you can consolidate your reports in less screens.
HTH,
Javier.

>Just curious, I've been building onto the same application for a while now, the specs just keep expanding. I've found myself creating alot of small forms with 2 or 3 controls on them to set up reports. Most of the time these are unique to the specific report, and can't be used universaly in the application.
>
>So the question, how many forms and reports and programs, etc can be stored in the project before is gets too large. Does it even matter? Is 40 forms too much, 100 forms?
>
>Any help would be appreciated.
>
>Thanks,
>Larry Morelli