To those people that use ADO ..
I am not a dot net kinda programmer .. however, I have noticed the Microsoft trend away from ADO ( sqloledb ) to the .Net Framework Data provider SQLNCLI.
The main difference in the two providers is Microsoft is pushing it's .net ( visual studio 2005-08 ) in that direction as well as the difference in RecordSets ( ado ) and DataSets ( ado.net ).
In doing some research .. the Dataset technology is more of a 'de-tached' version of the recordset .. in that you make the connection .. get your data in a cursor and then the Dataset is detatched ..
http://www.dotnetspider.com/forum/ViewF ... umId=33473
I am still using ADO and it works quite nicely in Windows 7 .. so I am not so concerned with it not being supported in the near future .. however, I am concerned with my 'distractors' that say ADO is an 'old' technology and should be not be used.
Like I said .. i am not a fan of the .net Framework .. when you have 5k desktops running an application .. I certainly don't want to have a version distribution problem just to run my application .. and I certainly do not want to run my application from a Citrix Farm and have to deal with all the permissions and nonsense with publishing my applications ..
Also .. the standard ADO class and methods to not seem to apply to ado.net .. If anyone has any comments or suggestions .. I would like to hear your voice.
Rick Lipkin
SC Dept of Health, USA