Arthur,

You don't say if the "/SQL" you are talking about is SQL Server or VFP's SQL or something else.
Since the client already has VFP and FPD applications, I'll assume that you mean VFP's SQL, especially since VFP7 comes with a OLEDB provider for VB, etc.
*IF* you are talking SQL Server, and assuming that the client doesn't already have it, there is considerable expense there.

If this client is considering VB.NET and .NET generally, then I have to say they may not be applying the best business sense. After all, all of the relevant .NET stuff is BETA and, as you've noted, VB is a complete re-write. There won't be a whole lot of competent VB.NET programmers around for a good while yet. The same can be said for developers for other .NET components too.

.NET exposure would be very good for you and your consulting firm. If the client is ready to undertake a project with you given all of the above, then I think you want to think hard about it and, probably, take it. As others have said, being paid while learning is the best situation you can get!

But if the client really cares about his/her business, I would think that getting into an UNPROVEN product set with UNSKILLED development people should be near the very bottom of their list. Of course it is hard for them to ignore all of the MS hype surrounding .NET, and MS is going to be pushing even harder over the next 12-24 months.

good luck,

JimN


>Hello all.
>
>I do business development with a consulting firm that has expertise in VFP. I currently have a prospective corporate client that has some VFP and FP DOS applications and they are considering rewriting in VB and/or DotNet.
>
>Can anyone provide direction as to why VFP/SQL is a better solution VB/SQL or DotNet/SQL?
>
>For starters, I can come up with the following:
>
>1. VFP is OOP which is a more efficient model (easier to build with and maintain).
>2. VFP version 7 is released and is built on a solid foundation. VB is going through a major rewrite. DotNet is in beta.
>3. VFP has 3rd party tools that enable web interfaces now.
>4. VFP is flexible with nTier (can build COM/DCOM - or it can use VB COM/DCOM)
>5. VFP is data bound which makes it easier to build against databases.
>6. VFP has a more robust development language.
>
>Question, How is VFP's performance against an MS SQL database vs. VB's performance?
>
>Thanks in advance for some feedback here.
>
>Regards,