>I am writing a large app that is going to several clients and I am wondering how to handle the various inputs required for reports ie; A/R Aging report requires a date field, an optional customer ID, an optional Salesman ID, and an optional 'number of days overdue' variable.
>I allow 'super-users' of the system to modify report layouts as required and I would like them to be able to add reports to the system. But how to handle these inputs that are required for most reports? Do I design a form class and show it and add objects to it in the init of the report? Sounds like a lot of work...
>
>We are using SQL 2000 on the back end and have made stored procs to actually retrieve the data for each report by passing them the parameters required.
>
>Thanks.

If the report layout is always the same, but only conditions change, you have to design a user selection criteria form, which would return your select statement (or where condition)... I have several classes designed for user selection form criteria, I'll probably publish them here lately, after I receive some feedback from Steve Kramer...