ADO.net Book

  • Thread starter Thread starter Jim
  • Start date Start date
J

Jim

Can anyone recommend a good book for ADO.net. I am a experienced VB-dao
programmer. I am having trouble trying to accomplish simple tasks with
ADO.net such as moving through a dataset. (eg. VB6 movenext, moveprevious) I
also am having trouble accessing a specific field in the database. I know
the methodology of ADO.net is totally different. I am getting frustrated
trying to accomplish simple tasks that I could do with DAO. Maybe I should
just stick with DAO?

MBS
 
Jim said:
Can anyone recommend a good book for ADO.net. I am a experienced VB-dao
programmer. I am having trouble trying to accomplish simple tasks with
ADO.net such as moving through a dataset. (eg. VB6 movenext, moveprevious) I
also am having trouble accessing a specific field in the database. I know
the methodology of ADO.net is totally different. I am getting frustrated
trying to accomplish simple tasks that I could do with DAO. Maybe I should
just stick with DAO?

MBS
Click to expand...

I suggest you google ado.net getting started as there are lots of resources
available online.

/Fredrik
 
3 books come to mind - each of who's authors are frequent contributors to
this ng.

The ADO.NET Core reference by David Sceppa -

ADO.NET and ADO Examples and Best Practices
by Bill Vaughn

Pro Ado.net With Vb .net 1.1: From Professional To Expert (US)

Couldn't speak any better of any of these books - they've all helped me more
than I can say.
 
There a lot of good resources online (and in our books). However, I've found
the biggest roadblock to learning .NET and ADO.NET is getting over the fact
that it's NOT the same as anything else. Yes, there are similarities, but
the mechanisms behind the scenes are totally different, the programming
interfaces are different (especially from DAO) and the way you handle data
is different as well. ADO classic or .NET will never be as good an interface
to JET as DAO. DAO is a JET specific data access interface. It's fast, light
and old (experienced). However, Microsoft stopped working on it a long time
ago so support will be a continuing issue. In addition DAO makes a terrible
interface to other data sources so if you're thinking about moving to a
better DBMS engine you NEED to drop DAO.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________
 
Bill,

Thanks. I think you described the problem well. I should probably stop
trying to figure out how to do a task like I did in DAO. I'm guessing I
would be better off looking at ADO.net as totally new way of doing things.

MBS
 
Back
Top