Is welcome any experience with this tool, How to use BO with Crystal Reports.

Darn, I knew you would say something like that .

Seriously, thanks, it does explain many things, and you are right, that kind of flexibility is not always needed by the end user.  So in my case it would be safe to do one of the following:

1. Design reports as I am doing, in the form where they will be called, and then remove the reports BBS from this form and the toolbox attributes since once the report is complete, they would not be used unless I need to add or change a field?
2. Or, could I create a ReportManager subclass in a temporary form used to just create all reports, then in each forms where the reports would be used, create an instance of that ReportManager subclass to use the report?

If number 2 can be done, I would prefer that path, since I notice that in the ReportManager you can have many reports and many Data Sources to assign to those reports, this way, I would have some sort of centralization at least to create the reports.

Edhy Rijo

You could do your #2 option, but the only thing I would caution on this one could be size and sluggishness of you get a lot of reports.  In our medical application, we will have over 200 reports.  This on a single form would kill it, but if you are only going to have a couple of dozen, then it wouldn't be that big of a deal.  Even if you go with option #2 and run into performance issues at design-time (or run-time), it shoulnd't be too difficult to break it apart if you had to.