>I think the only thing I really have a problem with is the FUD that claims once you leave VFP there is no more data handling, oop, RAD etc.
>
>Can you provide examples where best practice routinely involves changes of parent class? Why would you plan this way rather than (say) using (NET) interfaces? Serious question.

I had such a case when transitioning from VFP7 to 8 - I wanted to have a special kind of button, so I simulated it by using a container, a shape, and a label. Then the commandbutton in 8 could do all that, and I wanted to get rid of all the instances of my old button - couldn't just remove the old class and stuff a new one, because there were custom methods and properties involved, so I had to write a builder (which was fairly simple, actually). Another example is that you may have a few dozen regular (i.e. your standard general purpose class) textboxes with date fields as controlsource, that you now want to replace with containers with a specialized textbox and a commandbutton to invoke a date picker. Again, I'd write a builder, but if there's a more elegant way, the better.