This isn't surprising to me. ADO used the Fox cursor technology internally. Why shouldn't ADO .NET take from the best too?


>Hello:
>
>I've been learning a lot recently about ADO.NET. Wednesday at a Boston UG on .NET (100 people attent this regularly!) the topic was ADO.NET. It was clear to me that the capabilities of ADO.NET where taken right from VFP. All of the really cool stuff the speaker was showing off has been in VFP for 7 years now. When he talked about how you can check the original value of a table in a dataset with the current for concurrency issues, it got this huge applause. Instead of OLDVAL() and NEWVAL() ADO.NET references the oldval with Original_fieldname. On many other features, it was a one to one match with VFP.
>
>Conceptually it should be easy for VFP developers to learn ADO.NET.
>
>Datasets = DBC's, you can set relations between tables in a Dataset, you can query tables in a dataset, you can use ADO.NET separate from any backend if you need a cursor engine. The dataset can be persisted with ADO.NET versions of cursortoxml and xmltocursor.
>
>Any one else who can point out similarities that will make the use of ADO.NET easier for VFP developers should definitly post their findings!
>
>Thanks
>Harold Chattaway