Larry,

Thank you for explaining _why_ it's advisable to separate the biz classes. I hadn't thought of that angle.

Alex


>I agree with Craig's suggestion to break out UI and non-UI classes.
>
>And to expand alittle on that subject, I would have several business object class libraries instead of grouping them under one large library. The reason for this is team development. If all the business objects are in one class library then only one developer can work on that library at a time. If you break them out in to different VCXs, development time can be used much more efficiently (IMO).
>
>You could have a master business object class in the _abizlib library (opr you could add this class to the framework level library. Then all your business objects would subclass from it.
>