Hola, Javier.

>For me one of the best things would be if they happen to add a small local engine to .NET, or make NET more (and I mean much more) data focused. This way it would be like a succesor to VFP. Taking into account that the vast majority of programming in the world is made in the businesses, and are all about moving and crunching data, I still don't know why the hell they have spent 30 years to realize that we need a data centric solution (like VFP), and not a a general programming language like the C-C++-C# saga. WHYYYYYYY?
>
>A local engine it's not only to be the repository of the main data, which can be in some SQL engine. But it is really usefull when you bring some set of data and want to do calculations, transformations, and local data manipulation, which is done a lot of times. I don't buy the idea that all data calculations can be easily done in SQL, no. What's the choice onece you have the data on your computer? Handling it with objects, data sets, and arrays? Isn't it much, much, much faster and easier to use it with local cursors? SCAN, LOCATE and REPLACE are great for local data handling, like it or not pure NET programmers.

.NET has all of these features you mention, at different levels of implementation. There is a lot already released to use, and there is a lot coming in the upcoming months. They already have a local data engine which is SQL Server Compact edition, and there is very interesting stuff coming around data handling, both server and client side.

It is really worth to keep an eye on what the guys are doing, even if you don't have a compelling reason to move now (and in many cases there isn't really).

Saludos,