Hello Malcolm,

Here's a few comments (for whatever they're worth):

>snip<
1. Abandon DBFs/DBCs and use MS SQL Server
>snip<

I haven't written an application using DBFs or DBCs in almost two years. Doesn't mean they're not important parts of VFP, just that when you make the switch to SQL Server (or equivalent) you have other options. I don't think you will miss them very much.

>snip<
2. n-Tier (COM)
>snip<

You're going to love it! There is a steep learning curve and it's a dog to troubleshoot, but the end result is worth it. Are you sure your clients are ready for it?

>snip<
3. Visual Basic
>snip<

Why not use both VB and VFP? I'm like you, I have been using the x-base syntax since JPLDIS (that was before Vulcan and dBase for any young squirts lurking around) and feel very, very comfortable with it. Suggest to your team that they try at least one project in a mixed VB/VFP environment. Let the VB programmers do what they are good at and you do what you do best in VFP.

I'll probably get flamed for this next statement. I don't know what kind of shop you have with respect to staffing levels and depth of expertise, but if you are the last VFP man standing and there is no backup, it may be a valid business decision to move to a single platform. It all depends on how much time you can devote to programming as opposed to other business demands. This is a hard decision to make and for me to give up VFP would be equivalent to losing a long-time friend.

I wish I could give you more help.

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