Printable View
All the tutorials and stuff that I read on ADO.NET use DataSets and DataTables and the like...but I think I discovered that Recordsets are stil supported in .NET (??) ...so when is it ideal to use a recordset in ADO.NET ??....or can it just be done without and the people who still use it do so because they're ADO programmers who love their RS ??
Well, I havent' used a recordset yet... didn't know they still had support for it in .Net, but anyway, it would be for backward-compatibility.
Recordsets are not supported in ADO.NET. The closest thing to a recordset is the DataTable which is in a DataSet. Besides, DataSets & DataTables are way cooler than Recordset.... more flexible, more functionality and provides a great way to lump related data together (even if they are from different sources.)
Tg
Added Note: Recordset can still be used, IF you use ADO.....that being the old "classic" ADO.
You can set a reference to MSADOXX.DLL in your project, and use ADODB.whatever as you did in VB6.
You should have your reasons for doing this, though. I was doubtful about datasets and datareaders at first, but I later realized that they are a good thing.
I currently use ADO and recordset in VB.NET. I choosed this way because I wanted to be free to use pessimistich locking, that is not supported by ADO.NET. Recordset are very easy to use, also. I think it's possible to use DAO, too, in VB.NET, but I'm not sure about this. The bad thing is: using ADO in VB.NET you are with a foot in the past and with other foot in the present! Anyway it works greatly, but if could restart my project now, I'd change my choice and I'd use ADO.NET and its instruments, in order to be aligned with the whole community and to become experienced of that Object. :wave: