Hi Brenda,

the recent outsourcing aticles I've read indicate that if the application is specific to your domain, and tightly integrated into the business process, it should not be outsourced. InfoWorld, March 8 edition, has relevant articles.

As to why VFP: it's easy -- productivity. We created, with a company where I spend most of my time, a 300-entity app, not including metadata tables, in under 6-person years. It's been selling for a year, and installs are lined up 3 months in advance. In .Net, that would have been 60 person-years, minimum. Even at outsourcing rates (which have climbed), it would be more expensive to produce in .NET. Assuming that it succeeded as an outsourced product: and there is pretty good consensus that your company would have to fund an on-site (in India or Bulgaria or wherever) manager for the project, in order to have it succeed.

VFP, and the tools that are available to work with VFP, are the best!

Hank Fay

>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