John,

>You don't even dared to dive into the details of ADO.NET with me, because you knew you would not be able to defend your standpoint, You did end our discussions with me when I could prove that you did not know what the hell you were talking about when it came to the enhancements in VFP8. When it gets real technical you don't seem to have anything to say and revert to rethoretical meaningless lawyer talk. Could it be you simply don't know and just are BS us ??

>I end discussions with you because you because it is not a productive excercise.

It is great to hear that you won't respond to this message.

>To say that I end discussion because I cannot defend a point or because I do not know what I am talking about is not a reasonable conclusion.

The prove was delivered in another threat. You surely are able to browse back to that one.

>One has to greatly discount what you have to say in light of statements from you that conclude ADO .NET does not have a local data-engine component.

And I still will say that. ADO.NET is a outgrown intermediate data storage object, period. You can do basic stuff, but you can't even create a database and store the data in a native format. You've got to rely on another RDBMS. I don't know any RDBMS that is depended on another RDBMS to store its data. Hell you can't even do a SQL SELECT command on the local data with ADO.NET. Your definition of what a local database engine is is seriously flawed.

>As for the "enhancements" to VFP 8. It is not that I am not familar with them. Rather, I don't care about them.

so you're not familiar with them.

>Why? Because in the pantheon of improvements to the product since 3.0, they rank near or at the bottom of the list.

No you already made you choice. Promote other to do .NET and watch them fail before you yourself jump entirely to .NET.

>With the exception of IntelliSense in 7 - there have not been many enhancements that have made the product materially better.

How about VFPs 8 Support for XP themes ? How about TRY CATCH FINALLY? surely great enhancements. How about the new view designer which is REALLY an improvement from earlier versions.

What to think about the upcomming enhancements in VFP9, Greatly improved SQL SELECT Support where the keyword is 'no limits' and smaller and more effictive indexes.

>The bottom line Walter, you are a Fox-knob that continues with knee-jerk responses that Fox is always better and everything else sucks.

Liar, I never did say this and never will say so. Retrieve one message where I said this ! You reading things that I never said. VFP is great for desktop applications. .NET is great for internet applications. SQL server is great for enterprise database solutions. Delphi is great for building powerfull and blazingly fast components. C/C++ is great for building powerfull DLLs and components. Crystal Reports is great for creating great reports. Assembly is great for stuff that needs the ultimate speed. MS access is great for end users to build their own amateur databases.

I'm proficient in VFP, SQL Server and Crystal Reports and could produce decent C/C++ code if I have to.

I've always dismissed VB and now VB.NET. Also .NET for winforms as suitable environments for desktop database applications. And that of course is your problem. I highly appriciate the local and powerfull database engine that AFAIK not any other compatitor has. It makes VFP unique in this sense.

>Fox-knobs as a class - are people that are incapable of objective/reasoned technical discussions and basically

More lies, assumptions and typical JVP terrorism. I've never seen you come with technical details. Everytime it gets too technical you're bailing out... coward...

>, are in denial and get personally incensed at the fact that the other 99% of the development world (including MS itself) has tossed FoxPro onto the pile of irrelevant/obselete technology.

Ohhhh man, you do think you know it all do ya? I'm wondering what Ken thinks about this very same statement? If you only knew how many VFP and even FoxPro applications are running in the world and in what industries, you would have a lot more respect for the FOX.

If VFP was a obsolete technology why is it still under development ? Why does MS still have no alternative to VFP data centric language ? I suspect that they are working on that. Maybe not in VFP, maybe in a future .NET version, but as long as it is not there VFP is not an obsolete language. As long as there are things that can be done more efficiently and easier than in other languages it is not obsolete.

Walter,