The following compares vfp favorably to VB,VC++, and MS Access:
http://msdn.microsoft.com/vfoxpro/productinfo/faq/default.aspxThe bottom line, though, is that if they're willing to spend time and money to rewrite the app completely, then that's probably what's going to happen.
However, there are many arguments to be made to just take advantage of existing vfp code with the newer technologies. This is
very possible with vfp. You can create web applications with vfp very easily and you can easily call VFP methods from .NET (thru interop). IMO, this would be a responsible way to take advantage of existing vfp code and get feet wet with new tech developments...
>I work for SunTrust bank and support a medium sized VFP 6.0 app. The applicaiton is for real estate lending, both for individual mortgages and for large builder developments. We want to push out a upgrade to the product and we are stuck in committee. Everybody in committee wants to know why VFP? They are now even talking about sending our app to India to be rewrtitten in .Net. Of course you understand that these are a bunch of business suits who know nothing about the applications, the code, VFP or even .Net.
>
>I need some ammunition - maybe some stats or a white paper - that VFP with some other trendy languages like .Net. Need something that shows VFP is a good language and database. Does anyone have anything?
>
>Thanks
>
>Brenda
