>Depends on the reasons. IMO, simply because it doesn't do "record processing" but rather, "set processing" is not a good enough reason.

That is a very flawed summary of the complaints of local data processing capabilities of .NET. and really confirms you do not get the argument at all. It is all about handling data on the client side. In a nutshell: Data that ought to be relational, whether factual data or meta data, should be treated the same way, whether on the server or on the client. Good record and set oriented dml on all layers will help you create the ultimate flexibility to write highly (meta) data driven applications. VFP provides that transparancy over all layers. .NET (Currently) does not. In the latter, you'll have to use very different (propriatory and backward) techniques to handle the same data.

You and everyone else can ignore that, and anyone could argue 'it does not matter to them' or 'You can achieve the same differently', but anyway you cut it: Its backward: Data is data and should be handled in the same way everywhere.

Here we are in a forum that is about developing databasebase applications, and I'm stunned that so many vocal people, simply don't get 'data' up here. Even microsoft (finnally) itself has identified the problem in .NET, why are you guys ignoring that? Probably because it is of little value to you as you don't need that level of transparancy over all layers. Well there are developper who do value that, and there seems to be a high level of ignorance towards this group, just like was happenning 5+ years ago when VB people talked about VFP.