I'm with you on the behavior and many of the current methods are virtual and
overridden for the instantiated objects, but its syntactically and logically
convenient to use static methods -- they retrieve instances of the class
through a query, so they are operating like a factory:
DataTable dt = Prospects.Retrieve("state = 'TN'"); // retrieve all
Prospects where the State is Tennessee
Right now the static methods are declared on the derived classes, but I can
push these into the base class and just pass in minor information. The goal
is tidyness, more logic in the common base class and less in the derived
class.
john
<Carlos Swrote in message news:up*************@TK2MSFTNGP06.phx.gbl...
>I would suggest going away from static methods in this case since what
you're looking for is polymorphic behavior. I would make the method an
instance method and mark it as virtual in the base class and override it in
the subclass.
Carlos S