dao vs. ado

[Kan D.]

somebody tell me the adv/dis-adv to using ado vs. dao

Kan

 

[Douglas J. Steele]

In general, if you're working with a Jet database (MDB), use DAO. If you're
using another DBMS, you may want to use ADO.

You might be interested in seeing what MichKa has to say at
http://www.trigeminal.com/usenet/usenet025.asp and
http://www.trigeminal.com/usenet/usenet017.asp

 

[Jamie Collins]

You might be interested in seeing what MichKa has to say at
http://www.trigeminal.com/usenet/usenet025.asp and

There are some things on the list that are 'grey areas', IMO. One of
the points seems to be a fallacy: one *can* use ADO to create user and
groups and specify the PIDs (as detailed in
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k/html/acadvsql.asp)
e.g.

CurrentProject.Connection.Execute "CREATE GROUP Billing Gu294JxP1m"

http://www.trigeminal.com/usenet/usenet017.asp

I think the second article is now out of date e.g. considering the
Access 2007 release.

Jamie.

--

 

[Jamie Collins]

somebody tell me the adv/dis-adv to using ado vs. dao

My summary would be, there are some things that DAO can do that ADO
can't (see the list Doug linked to) and vice versa (notably, ADO can
use the Jet 4.0 functionality and DAO generally cannot).

I think the ADO model is nicer to work with e.g. unlike DAO you don't
have to explicitly create and destroy objects and in a certain correct
order. ADO objects are more feature rich e.g. recordsets can be
disconnected and/or fabricated and/or hierarchical and support
more/improved properties and methods plus, because the can be used
asynchronously, they have events. But then anyone *would* expect ADO to
have improvements, having being built on the success of DAO and learnt
from its failures. I choose ADO because code maintenance

On the other hand, I understand DAO like-for-like offers better
performance. Also, there is a greater body of work in DAO for
Access/Jet e.g. on google you are more likely to find a DAO code
example than an ADO one.

Is anyone forcing you to make a choice, one way or the other? I get the
impression most of the Access MVPs use both ADO and DAO; I think anyone
would be best advised to do the same to be able to enjoy the best of
both worlds.

Jamie.

--

 

[Larry Linson]

I think the second article is now out of date
e.g. considering the Access 2007 release.

Access 2007 is only in beta; it has not been released. Until it is actually
released, you can't count on any particular content being included or
excluded -- that's the way release cycles work.

Larry Linson
Microsoft Access MVP

 

[dbahooker]

LIAR!

if you're using _ANY_ database use ADO so that it's easy to migrate
databases


-Aaron

 

[Jamie Collins]

Access 2007 is only in beta; it has not been released. Until it is actually
released, you can't count on any particular content being included or
excluded -- that's the way release cycles work.

Changes to the engine have already been 'announced':

http://blogs.msdn.com/access/archive/2005/10/13/480870.aspx

Do you genuinely believe there is *any* chance MSFT will 'rollback'
Access 2007 to the Jet 4.0 engine?

Jamie.

--

 

[dbahooker]

JET is DED.

ADP won the war.

lose the training wheels; kids

-Aaron