>Go to www.classx.com and download Superclass utility.

Thanks for the reference. I've downloaded it and I'll try it.

But I am curious, why doesn't the Edit-Parent-Class-Method button of the Form Designer allow access to the method code of the controls that a subclassed form contains? I see by investigating the code generated when a form is saved as a class that its contained controls are saved as instantiations of objects (as opposed to being subclasses).

But why not allow access to edit these object definitions (or at least view them) the same way one can view (and edit) the parent class of the containing form? Is there some OOP-ish reason for this or is it just a desirable feature that has not been implemented in VFP 6.0?