>Example, for me, my application is written in VFP. Therefore, should I, and those in my shoes consider:
>
>1. VPF/SQL
>2. Move to VB/SQL
>3. The whole .Net thing
>
>Hopefully, your contributions to this thread will help all concerened in probably, knowing more about VFP and other alternatives.
>
>Thank you in advance.

You have two possible solutions:
- cost-effective
- most advanced

If you need of fast, cost effective solution because you take care about investments, performance, term of implementation choose VFP/SQLServer.
Your VFP developers very easy, keeping some rules can convert standard VFP to VFP/SQLServer.
How much time this solution will be enough progressive - may be 2-3 year, after that may be you must switch to .Net or who knows. VFP IDE and .Net CLR are different and may be if you proceed large databases you will be forced to work with VFP. May be it will have not some nice features like .Net apps, but it will be fastest.

If you look in the future think about .Net with all expenses and problems. May be after 2-3 years performance of VB.Net will be better. Retrain you programmers, hire additional, because development of databases with VB.Net consumes more time. Try to pile some experience with .Net. May be firs version of the product will be very bad, but second after 2-3 year will work depend on requirements of company. Or company will switch requirements to possibilities, which can offer .Net