Malcolm,

First, my sympathies.

I think the killer is your last line, where you note that you have big projects ahead. The reality is that big projects should be tackled with an OO language, which VB is not. Otherwise, the more work that gets done, the less maintainable and extendable is the project.

Just yesterday there was a thread on this, and a lot of good points were made, and a lot of sources were given for such things as MS's commitment to VFP (you'll need to kill the "fox is dead" myth). Check it out.

Good luck, and please tell us how it works out.

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