VFP is not dead, I can see that it's alive and kicking. It's now grown up, so it doesn't need the support from its parent. And its parent never supported it well anyway. That's how I see it.

>Time and cost are subjective. Considering that VFP is dead and now unsupported, will it cost more to keep that app alive in the long run than it would be to re-tool it in something more modern?
>
>
>>Rewrite always takes longer and is more expensive than originally estimated.
>>
>>
>>>Hi All,
>>>
>>>A large Corporate Client of mine was prepared to update a VFP 9 App until they went on Microsoft's VFP Main page: http://msdn.microsoft.com/en-us/vfoxpro/bb190225.aspx and got scared by the statement:
>>>
>>>"Note that Visual FoxPro 9.0 is the last version and was published in 2007. For a great solution for building modern business applications, take a look at LightSwitch in Visual Studio 2012"
>>>
>>>which they interpreted this as "Microsoft is telling us to use another product."
>>>
>>>So we have another case of FUD - Fear, Uncertainy Doubt..So I have to reassure them..
>>>
>>>Any articles around to make the business case for VFP?
>>>
>>>BTW, Already own the wonderful Henztenwerke Book: The Business Case for Moving (Some) Business Applications to VFP in 2013 - Highly Recommended