Kevin,

That's interesting. In general, I consider a rewrite for the sake of moving to new technology a bad business decision. It would be a colossal mistake for us to do that at this time, but I realize other businesses have different circumstances. Maybe they are short on Fox talent. Maybe it won't cost that much to rewrite. In any case, the only real ROI in this situation is that the company no longer needs a Fox developer, which could be a big deal to them. It's beside the point anyway. We know that the industry revolves around actual decisions, not whether they are good or bad.

>
>
>What version of Fox are these apps running? Do you think they make full use of VFP features, or are they just ports from Fox 2.x? In other words, would a rewrite be in the plans even if they stayed with VFP, or is this just a way for them to get off of Fox and on to .NET? Just curious.
>
>
>Good question, and actually 'yes' to all. One was a Fox2x app, one was a VFP8 app, one a VFP8 app that was really 'written' in VFP7 and then recompiled in 8 with a few tweaks.
>
>All of them wanted a clean break. I really wasn't involved much in the decisions - the plan was to bite the bullet, believing it was best to deal with 2 technologies (.NET and SQL) instead of 3. I do realize that some places want to take an incremental approach, because of time pressures or other factors - David Stephenson talked about this in a post last month.
>
>The growing popularity of frameworks like Mere Mortals and related/follow-up consulting makes the concept of writing it all in .NET a little more attractive and palatable.
>
>Kevin