>Craig this is an interesting perspective. This approach could allow the development of a either an enhancement to ADO.Net or an option to ADO.Net, Perhaps FPDA.Net (FOXPRO DATA ACCESS).

From the article, it seems that the VB and C# teams are looking at doing things differently, so that makes it language based. However, in the end, they both have to compile to the same runtimes, which tells me something common. (hmm..that sure left everything open to interpretation....I could write marketing stuff for MS *G*)...

I think something in ADO.Net makes sense.


>
>After working with ADO.Net for a few months I have been very frustrated with what seems to me to be "excessive" plumbing to get to and modify data. I suspect that I am not the only developer which has had this experience. Since this is a VFP related community center, I wonder whether this is the right forum to express those frustrations. I know there is a .Net area here on the UT, but it does'nt seem to have the intense following as does the VFP area.

I had trouble grasping the data access stuff until the last couple of weeks. I'm working through the book, "Beginning C# Databases" from APress and one paragraph made it clear to me. Why no one put it this way before, I don't know. The Connection object connects to the data. The DataAdapter holds the SQL statements. The DataSet holds the data. You do have to wire up everything, but it now makes sense to me.

>
>Do you know of an ADO.Net community site like this which is monitored by MS team members, MS movers and shakers? I we were to extol the data handling simplicity and efficiency of VFP as compared to ADO.Net perhaps we could exhert greater influence on the ADO.Net/VFP feature development.

There are several sections at http://forums.microsoft.com/msdn that may work. They aren't ADO.Net specific, but intermingled in the different forums.


>
>Glenn
>