>Like I'm sure a lot of folks here I recently got a message in my Inbox subject : "Moving from FoxPro 1.x/2.x to Visual FoxPro." and my first reaction was that somehow this had been stuck in a queue in a mail server someplace since 1996 and was just now making to to me ... from Whil Hentzen. If I had not seen 2012 in the message body I would have remained convinced.
>

As developers we like to just say, "dump that old crap and move into 'X' technology". Honestly, most of us HATE working on old code. We love to gloss over the fact that the real world is a much more complicated place than the one that lives in our head (it's probably why most of us are so horrible at estimating how long things will take). From a business perspective, throwing out 15+ years of development time for something new is pretty damn risky. I've seen my fair share of rewrites taking significantly longer than originally expected. You know, "Just keep this old system running for 6 more months until the new system is up and running". Three years later and the answer is the same, "Just 6 more months until the new system is up and running". A port to a later version of VFP, then starting to do things like upsizing to SQL Server, then eventually to some new dev. platform may be a much better solution (it can also take a really long time).

So I guess I'm just saying that a rewrite/port to a later version of VFP can actually make a lot of business sense. It can also be a horrible idea. It depends <g>

But I'm with the people that shudder about having to touch FP DOS code. Not for me, if I can help it - I push that stuff off onto co-workers.