ADO.NET vs ADO question.

  • Thread starter Thread starter tascienu
  • Start date Start date
T

tascienu

ADO used to do simple little things like these:

Dim rs as new RecordSet

' Create new record...
rs.AddNew

' Add Information...
rs("Name")="Tasc"

' Update...
rs.UpdateBatch

' Get new record ID rightaway...
NewID = rs("ID").value
 
No such thing as a recordset in dotnet,.now you have datasets. They seem a
bit more complicated than you wrote in here, in my limited experience.
 
First, understand that the only things that ADO and ADO.NET have in common
is the fonts ;) If you keep that in mind and approach the two interfaces
with an open mind you'll be better off.

Both interfaces have connections, commands and ways to fetch data. They both
have ways to update data and clean up after themselves. ADO.NET is far
lighter--it puts more responsibility on your shoulders to provide code to
add, change and remove data from the database. It does not generate this SQL
for you like ADO did. However, Visual Studio has wizards that can help
generate these SQL statements for you if your design is simple.

I suggest you get one of the books (like mine) that walk you through the
process of transitioning to ADO.NET. Mine is specifically targeted to ADO
developers converting to ADO.NET.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Back
Top