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.

>Mike,
>
>Usually instead of copying the class to a new place and modifying it, you subclass it. Subclassing container the classes with other objects inside them can be problematic though.
>
>To get your subclasses used in forms will involve opening the forms as tables and modifying the classloc and class fields. You can do this with a .prg that can easily handle all your forms.
>
>>I am working with VFP 3.0, and built a form using the form wizard. Now that I understand a little bit more about how to use classes and class libraries, I would like to make some changes in in the wizstyle.vcx base class to make my form work better. However, I would rather not alter the original wizstyle classes. Is there a way for me to make a copy of this class library in a different location, and re-associate the form's base classes to this new class library?