Hi,

I kind of agree with Bruce.


Remember that Visual Studio and Visual Studio.NET are two separate languages. VB and VB.NET are two separate languages. C/C++ and C++.NET are two separate languages. This mean that any program written in pre .NET languages will need to be be re-wriiten. If VFP goes to VFP.NET, all programs currently written in VFP will have to be re-written. This might result in no new updates to VFP during a transition period to a VFP.NET language. There is no guarantee that the VFP client base would be happier with a VFP.NET application. As a matter of fact, it would likely make VFP application much slower, more complicated to write and maintain, and a pain to distribute.

Microsoft strategy is:

Write your app in any of around 20 different languages, compile it under the .NET CRL, and then run it under windows.

Sun Java strategy is write the application once using the java universal language, then run the application across any platfrom.

Dot NET and Java are identical twins. According to some web threads I've read, java and c# are so much alike, java apps have been download from the web and run complete unchanged in C#, and vice versa.

If moving to a new language will require a complete re-write of everything, and the only difference between .NET and Java is that .NET will have a Microsoft Window platform lock-in, while jave is cross platform, why not go to java if the world wants all apps to be written based on a three tier model with a java/.NET like interface, coupled to an expense enterprise class database server.

It seem to me that this would leave a tremedous void between the Access office desktop database on the low end and MSSQL on the high end.

LelandJ