>>Hi Vlad
>>
>>Yes I can see how you also would require a very efficient way of accessing the parent class code.
>
>It is not quite clear for what you're talking about. Parent class code could be called using 'dodefault()' function iside of the method of the child class.

Sorry Vlad I should have said Editing the parent class code.

>
>If you want to automate forms changes by reliable way, you have to work with VCX file as with DBF file. For example, by this way I made a simple routine to change parent class of all headers in grids to custom class. By this way you can edit and correct anyting you want. This way allows to do a lot of things. However, it is complex one and can take some time for complex changes. YMMV.
>

Aha yes it would be possible to do it this way.
However taking my thoughts a step further I can now see why no one has bothered doing it. If for example class existed that always showed the parent code and always implemented any changes in subclasses straight into the parent then it would go against the entire idea of Oop and just leave the class as a tidy place for leaving bits of code.

I think this is an example of my brain unconciousley trying to drag me back towards the procedural way of doing things:)

I guess I will stick to using Supercls for editing parent class code as it works pretty good. I wonder if VFP7 has this functionality built in.