>To date, we've been programming in both VB and VFP. However, because we had recently decided on MS SQL Server, they want everybody to program in VB (one language). I know nothing about VB, therefore, could not come up with anykind of an arguement not to abandon VFP - except for VFP can do anything VB can and better.
>
>I am so comfortable programming in VFP and feel I can do just about anything with it. Just hate the thougt of learning another program just to do the same things that I could do in VFP.
>
>The group had decided on the following:
>1. Abandon DBFs/DBCs and use MS SQL Server
>2. n-Tier (COM)
>3. Visual Basic
>
>The final decision is mine, however, without a solid arguments, I could not burden the group with my bias and lack of knowledge for other programs nor was I willing to break the enthusiasm of the group - we have big projects ahead.
>
>Need your help on how to convince and/or argue keeping VFP and/or a middle ground where VB and VFP can both co-exist and be beneficial.
>
>Thanks,

Earlier this year (Jan 99?) Software Development Magazine stated that of all the tools in Visual Studio 6.0, only VFP was positioned for middle-tier components.

Another argument. While both VB and VFP can be used for front-ends to SQL Server, you have to do something with that data once you get it. VFP will kill VB here.

I've also heard of many shops/projects that moved from Fox to VB only to come back because VB couldn't handle it.