>The .NET model is to use ADO.NET, as in datasets, not VFP cursors since the VFP runtime is a separate and different runtime than the .NET CLR and framework runtime. The Visual Studio teams are working on adding more data-centric and databinding features to .NET programming, often referring to VFP for ideas and scenarios.

Ken,
here in Italy it's 1 o'clock, so sorry for my english, I'm just returning home from an Yes group concert....
I have downloaded and installed VS.2005 beta (just because I want to "touch with my hand") and I've used it for only 3 days now, but let me say that for what I've seen this features are really "a lot" of features: it's look like the are cloning VFP into VS.
I mean, there are:

- TableAdapters, which are exactly the same as VFP cursoradapter (in VS you can define more query, and use what you need)
- In Tools->Options you can define which classes (textbox, combo, ecc.) will be created when you drop table fields from the Data Sources Windows
- Again, from the Data Sources Windows you can choose if you want to create a grid or single controls when you Drag&drop many fields
- In the docs they talk about "local data" as a new "data feature" but they talk about Access, MSDE, but vfpoledb is not mentioned

and so on. (For other here, take a look at: http://lab.msdn.microsoft.com/library/en-us/dv_raddata/html/3d50d68f-5f44-4915-842f-6d42fce793f1.asp)
Now, it's easy to understand what will happen...
Let's call it a "VFP's programmers soft conversion" (but obliged) to .NET, or not?

Franco