>>><<
>>>Absolutely true. I don´t have first hand knowledge of how .NET works.
>>><<
>>>
>>>Thanks for the candid/honest answer... When commenting on .NET, be sure to qualify so people know who much weight to attach to your opinion.
>>
>>
>I don´t see the relevance. Why do comments on architectual missings / mistakes have anything to do with first hand knowledge HOW it works at the implementation level...
>>
>
>Because you make specific statements like "ADO .NET is not a local data engine" Or...."VFP is better because it is data-centric" - the latter implying that .NET is not data centric. i.e., you make conclusory statement about how .NET works - all without first hand knowledge of how .NET works.

By its definition ADO.NET is not a database engine. It misses characteristics needed for it to be that. It is all at MSDN. No practical experience needed here. The specifications do just not fit the bill. There is no need to discuss this over and over again. I've made my standpoint clear.

Walter,