DAO vs ADO

  • Thread starter Thread starter Michael Wong
  • Start date Start date
M

Michael Wong

Hi,

Just for curiosity, starting from Access 2002, how many people use ADO
exclusively without any difficulty for a mdb database?
 
"Michael Wong" wrote
Just for curiosity, starting from Access
2002, how many people use ADO
exclusively without any difficulty for
a mdb database?
Click to expand...

None. That's because the builtin functionality of an MDB is DAO-based. The
closest you could come would be to use all unbound forms, and recreate
functionality in your own ADO code, but things like the RecordsetClone would
still be DAO recordsets (and that would be the case wheter or not they were
used).

Believe me, creating anything but the most trivial database with all unbound
forms is not "without any difficulty".

Anyone using "ADO exclusively" will be doing so in either an Access Project
(.ADP or .ADE) or Data Access Pages (DAP). In my experience, working with an
MDB seems much simpler and less effort than working with an ADP, but that
may simply be because of my long experience with MDB, and very recent start
with ADP.

I can say that there is vastly more excellent assistance available on
MDB/MDE than there is on ADP/ADE... even at the Microsoft site, where
there's been a reasonable amount of "promotion" of ADP as "an access method
of choice for the foreseeable future". (Microsoft's successor to 'classic
ADO' is already released in the .NET world, ADO.NET -- and is built on a
different object model.)

Larry Linson
Microsoft Access MVP
 
I came into programming Access with version 2000. In my VBA code I write
exclusively with ADO. Even though it seemed that many things were more
difficult to code, I have built many systems that are used by my clients and
now ADO is second nature.
I sometime regret not coding in DAO only because it is harder for me to
understand code written with it. (there seems to be a vast amount available
to access over the net).
Just my opinion.
 
Bill, Larry, thank you for your reply.
I've read that ADO is going to take over DAO, that's why I was asking the
question. For the moment, I have ADO and DAO codes mixed-up in my Access
database and indeed DAO is much more easier to code than ADO when it comes
to bounded form.
What is Microsoft planning for future release of Access? Will DAO be going
to be less supported? Or maybe ADO.NET will come into Access?

Anyway, don't worry my questions. We should still have a few years before
seeing any change in the programming of Access.
 
Back
Top