Paul,

Your reply and your contribution to the "Subclassing mm.net web controls" thread help greatly.

I know a couple of former vb 6 people doing vb.net using all classes straight out of the .NET Framework. I am very shocked to find that they would consider that as the best practice even after I explain what we usually do with VFP base classes.

Chen


>>
>>My feeling is that I need to subclass all of them (which makes me feeling safe). Since this decision will have profound impact ever after, I really need to hear what you say.
>>
>
>You're right, you will probably want to subclass the various UI components before using them in your application. I would also subclass the mmBusinessObject. A lot of the other components in the framework can be swapped out easily enough for other sets of classes since they are instanciated via the Factory object (see the help for more info on which classes), so I probably wouldn't worry about subclassing those right away (since it's easy to do later on an "as needed" basis).
>
>Maybe other people have other suggestions for classes you should subclass.