>
>What real good is a "premier middle tier development tool", that being where the business rules are enforced and the data requirements are determined. This stuff would generally get only marginal benefit from OOP, common procedures/functions being just about as useful for such logic.
>
>Regards,
>
Jim,

I would disagree, OOP allows for the inheritence hierarchy to define the public interface of a large number of different sepcialized classes for the middle tier objects. In my business tier class design there is one root class that defines all of the properties and methods for all business objects, then there are various subclasses that have been specialized to handle specific business issues.

Full OOP implementation does make a difference in how easy it is to do this and in how thorough the enforcement of the interface can be. Well designed proedure libraries can appraoch the same level, but without inheritence the ability to provide a common interface for all business objects is left up to the developer to make them all the same. This is too easy to add a parameter to one or more that causes them to be different.