Bret,

The only time I ever even looked at the stuff in wizstyle is in testing some of the sample code in VFP. I've never used them in production code where everything is derived from my own first level subclasses of the VFP base classes.

>I would not subclass anything in WIZSTYLE. When many people here told me of the shortcomings of WIZSTYLE, it became my goal to phase it out, rather than perpetuate its use through subclassing. When I started modifying those classes, I copied them to my own class library and changed their names in my library (from the command window, I think) before I ever used them. Then I ripped out the instances of WIZSTYLE classes and replaced them with instances of my modified versions. That wasn't hard, because WIZSTYLE doesn't have base forms (at least in vfp3), and the txtbtns class, which is the core of WIZSTYLE, can easily be replaced with another button container. Since I still use some unmodified WIZSTYLE classes, I continue to SET CLASSLIB TO wizstyle ADDITIVE.
>
>The tricks the others are giving you for changing the class of existing objects will be most useful for changing the class of all your textboxes, labels, and other individual screen controls. I have never bothered to do that.