In .NET this rearrangement would have been trivial (and pretty much unnecessary anyway) In VFP it is a project.Certainly I can imagine the VFP issue if you want to move parent classes from one vcx to another without breaking all your child classes. Not that you care much any more ;-) but one solution would be to use the class browser from vfpx to convert your vcxes to prgs, after which altering parentclass isn't such a challenge. That would assist with source control as well. Afterwards you could leave everything in prgs so you don't get bitten by this problem again, or you could try using prg2vcx to convert it back if you have other reasons to include the vcx in your project.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
