I picked the kBizObj to look at and was surprised at the size of it from an interface point of view.

( Not counting the standard VFP Methods/Attributes)
Public Methods: 100
Private Methods: 13
Public Attributes: 44
Private Attributes: 17

First the shear number of Public Methods makes me wonder if this is some sort of Swiss knife class and the fact that ratio of public to private methods gives even more credence to that thinking.

This is coming from a guy who believes that there should be something like 3 to 1, or better Private to Public methods in a class, classes should be very focused and use runtime aggregation and composition to bring in other ablities, and thinks that no attribute should be public. E.g. all class data should be encapsulated and must be dealt with via Set and Get methods.

I have not yet looked at other classes to see if this is standard or an anomaly.

Then again maybe because it is a framework, optimization is a critical feature, and runtime aggregation and composition rule-of-thumb has to be broken.

Oh well this is looking to be a very long and interesting learning curve.