>>It depends on how you convert. Now that I have more time, I've come back to my converter that I gave up years ago. It creates real VFP forms, ports the code into any framework (well, my framework for now - I need a conversion gig to try it on) and generally should switch the code into something very OOP - once we get rid of public variables :). And yes, it has none of the problems listed above... except the #name directive which I never used, but it shouldn't be too hard to add.
>
>So? Are you - at the end of your crusade against converting :) - now suggesting after all that conversion can be done, but that it should be done with your tool?

Or with an equivalent tool, i.e. with something that would output real VFP forms, just as if they were edited manually in VFP, or using whatever tool a particular framework may offer.

> In that case, make it available to Samuel and use him as the çonversion gig to try it on'. May be an interesting experiment.

Frankly, I'm trying to make some sort of living, i.e. this wouldn't be free - but would be half my regular rate while I'm developing the tool. As I said, it should do multiple frameworks, but so far I have only my apps to convert, and my framework is sort of getting nowhere. Always something more important to do :).