newbie14, you are asking alot of questions, but we haven't seen any effort on your part to determine what you need.
Don't be afraid to spike some code with a trail version of a reporting package. We cannot answer every question concerning your specific project. we can point you in a direction, but you still need to take the lead to determine what solution is best for you.
if you have questions about a specific reporting package contact the vendor for details. They will be able to answer questions about costing, product features, etc. Again, you still need to test the software yourself.
I echo AlexCuse's comment as well. reports are another form of GUI. you do not have 1 webform for every single request (at least I hope not). Why would you want/require a report to do the same? I would bet you are actually creating more work for yourself in the long run with this approach rather than saving time in the future.
There are all kinds of articles on the net about architecture and software design. OOP isn't about resuablitiy. It's about encapsulation.
article on the topic
GUI (including reports) should serve a very specific, single, purpose. If it does more than 1 task it will complicate maintenance dramatically. In then end you may end up with 100s of reports. but each report fulfills exactly 1 requirement. you can modify (add, edit, remove) a given report without impacting any other reports.
Jason Meckley
Programmer
Specialty Bakers, Inc.
faq855-7190