>I've been putting together some information off the Wiki, bits and pieces from the Microsoft website, etc. to answer the question, "Why FoxPro?". Has anyone been down this road already? Any links, or things I absolutely should include. I'd like to have this info handy and in a nice format so that if this question comes up, we'll be able to answer and provide our customers with enough information that they'll come to the same conclusion. This is part of our overall sales-pitch, assuming the question comes up. Obviously, we'll suggest different technologies when it's appropriate (eg. SQL server, .NET, VB, etc.). I want this to come across as a balanced decision, not as though we're a one-trick pony (we are balanced and VFP, while our primary tool, isn't the only one we're confortable using/recommending).

If they suggest using .NET, then you should suggest that VFP is used with ASP.NET. If they suggest SQL Server 2000, then you should suggest VFP with SQL Server since half of VFP developers use SQL Server with VFP. If they ask what tool you will use, just say MSDN which includes VFP, VS .NET, SQL Server, Windows, etc. Of course you can often build a complete application with VFP alone, but I'm just suggestioning these things for you to bring up if needed. You can give them my email address to ask me any questions if you think that would help at any stage of your efforts.