I am considering creating an object class that could potentially have a large number of methods to use - sort of a generic reporting object. However, I don't know if instantiating that object will incur an undue amount of overhead.

Would it be to my advantage to break it up into smaller objects?


Thanks in advance for your comments.

- - - - - - - - - - - - - - - - - - - - - - -
In God we trust, everything else we test.

I would assume that it would always be better to break them apart into logically separable units. However, this also depends on how you use the class. If the class is a large library of shared function (no class instance required) then you might not be gaining much by breaking it apart.

The purpose of most of the methods is to request stored procedures and return a dataset to the calling page.

- - - - - - - - - - - - - - - - - - - - - - -
In God we trust, everything else we test.