It appears that you have some good points here Stephen. I cannot argue against your comments listed below. What I am referring to in the advantages of FoxPro versus .NET is in the ease of use and data handling, or the command language. You cannot go to .NET and have the same function language capabilities, unless you get the VFP/.NET Toolkit. I am also saying that the data handling advances which were made in .NET originated from FoxPro gurus on that team. It was because of their FoxPro experience and thus recommendations that we have a better Visual Studio.NET.

It is anyone's guess where Visual FoxPro will be in a few years; it is unfortunate that Visual FoxPro has been treated always as a red-haired step-child as compared to the VB/C++/SQL Server group.

And yes, the 2 GB limitation is a PITA, but isn't that an operating system problem/limitation?

>Do you want differences between the two or benefits of one vs. the other?

>OK, how about how well FP works with ANYTHING else and passing a DATE to any other program in a message, via OOP design?

>How about having a group of programmer working on the same project together keeping up with bugs, tasks and fixes?

>How about the constant desire to put all code bases into a .dbf style container . Just change the extension per source type, but it's all the same.

>2 gig is still a PITA and always will be.

>What if the next OS doesn't do the old DOS space?

>Shall I continue?