>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.

VB is no longer allowed for large systems here, it is considered a real "clunker" for anything very large. Vfp is still not widely used here (yet, anyway, though it is growing), but is considered a powerful front end for any sized app. Powerbuilder is commonly used, too, and I may grumble about it, but it's a respectable front-end for a large system, no doubt about it. In any event, as others have said, you should be looking at something with OOP...