what's so great about classes?

[Evil_Giraffe]

No, but "VB" is not the same as "modelling your problem domain with classes"

The revision you described would probably be best coded as selecting the report they want from a menu or some such, running some SQL on the database, getting back a dataset that you bind to a gridview.

It's still a report no matter how you dress it up. You certainly don't need a "Customer" class for this.


However, if we consider this in the context of a larger application, such as a Customer Relations Manager system, it would absolutely make sense to have a Customer class, and to have ways of searching for customers that fit certain criteria. You would have behaviour associated with the Customer class, however, and screens for interacting with the Customer instances. As described, you are still talking about a flat report with no associated domain behaviour - just scrolling through the data.