Bob,

Firstly FULL unreserved apologies about my assumptions.

Secondly, am I reading this correctly : you are talking about
modifying VFP_BASE.VCX (VFP5) to change the parent class of a
CommandButton, say, to be a class that YOU might have defined.
And are you talking about VFP5 or VFP6 ?

Also, what is the eventual aim of that ? Reason I am asking is
that I have always operated along the lines of sub-classing the
FoxPro's base classes and using those new classes as your base classes.

Or am I understanding the term "foundation classes" incorrectly
(I have understood it to be the same as Visual FoxPro base classes).

Thanks.
Michel.
================= Original message follows =====================
>Michel,
>I was reading up on using the foundation classes and came across the passage:
>
>Instead of changing _base.vcx, however, you should redefine the classes in _base.vcx to inherit their behavior from your own custom base classes ... You can use the Class Browser to redefine the parent class for a particular class.
>
>And as David pointed out, it actually works! Trying to incorporate the foundation classes into an existing app would be a nightmare without being able to redefine.
>
>
>Bob
>
>>Are you sure you've read that correctly ? You can certainly move a
>class from one class library to another quite easily, but changing
>the parent class I do not think so. Imagine : changing a command button
>class to have "FORM" as its parent class instead .... What nightmare !!!
>>
>>Michel.
>>===================== Original message follows ====================
>>>The VFP Docs indicate there is a simple way to change the parent class of a component from the class browser. How can I accomplish this without editing the VCX?
>>>
>>>Bob