John,

>>>Nobody in their right mind would say: I'm going to build a new app today and I'm going to make sure it mixes both Fox and .NET together...
>
>I assume we are talking about database apps since that is the VFP domain... so what sort of "new" database app are you describing here? I don't think there are so many truly "new" database apps out there- not like the pioneering Lotus 1-2-3 days when completely new paradigms burst upon us. Most "new" database apps are actually re-enactments of work already done by or for others. If the earlier work is done in VFP, there may well be a good business argument to retain part or all of it. I am of course speaking from a customer perspective there. Allow a programmer to decide and he/she may well prefer the excitement of starting over.


When I say new I mean new development for an application, not new paradigms. Heaven forbid there are enough paradigms out there to last us all for a lifetime already without our applications adding new ones <g>...


As i posted to Terry earlier, there are right and wrong reasons to move an application. I believe you've found firsthand what the wrong reason can be <g>...

There are many applications that simply need to be re-written because their codebase is too old, or the code has become to convoluted and cluttered with junk as applications tend to do over the years as new technologies are applied.

At that point it's a good idea to look around and see if other solutions than the original tool might work as well or better. I've said it here before, doing a conversion or re-write of a serious application, 'just because' is usually a recipe for failure. There's gotta be a good reason for it.