>>In addition, the learning curve in .Net is huge especially if we start from scratch. However, you have advantage if your app's processes are already COMponent based and probably you know either VB6, C or C++, or Java.
>
>If one has used VBA, will that be an advantage in moving to VB/SQL or .Net?
Again, depending on the urgency of the deliverables. It's unfair if we'll deliver the product to our customers half hazardly. I don't know VBA, only VFP and a little on VB.

>What about for those who do not know anything other than VFP at the moment? The future of support for VFP?

VFP/SQL Server is the choice, but make sure to make it COMponent based so that you can use those stuff in .Net.

As for support, well, we still have VFP8 although not sure if there is still 9. But IMO, enough time to shift to another language if we choose to. In fact there are still DOS apps I see in many offices, so, why bother? What we will do is offering our customers new versions of our products.