that, we will have to wait and see.
>After VFP 8, can we still see another one...WAIT AND SEE and/or uncertain right? But .NET languages will still be there after version 2 or 3 or 4 and that's certain. Look at what happened with VFP MAC, they released version 3.0 but afterwards no more because no more demand. The decline of VFP marketshare is saying the same message? And so it needs miracle for it to bounce back and it will not happen if MS is not interested on it at all. Making VFP to be the front end of SQL Server is another puzzle to me. Can the VFP Team surpass how integrated SQL Server with .NET is?
>
Do you run Microsoft? How can you be absolutely sure that there will be a version 2, 3, AND 4 of .NET languages? Besides the fact that like all Microsoft Version 1 products, you will absolutely NEED Version 2 to be useful, in which case the camp that says look into but wait to leap is on the right track.
Surpass the integration of .Net and SQL Server? I don't see .Net is being inherently superior in the first place, but it wouldn't be too hard to package a database object in the base class framework. It might irritate the third party framework vendors, but the truly saavy users would probably still use the third party framework for app construction anyway. That's all that's missing in VFP, some pre-packaged code so that you don't have to be an expert developer to make the SQL connection, but it is already available from various framework vendors.