[AccessD] DAO vs ADO

1) they can be mixed but both references have to be set ...when identical 
functions are included in both object models Access will use the library 
first referenced unless you specify otherwise ...I specify by default just 
to be certain. As for differences, look at the object models ...DAO was 
designed around Jet and ADO around SQL db be's ...when using mdb/Jet be's 
DAO is usually much faster and has a better object model ...the reverse is 
true for ADO ...MS led everyone to believe for years that DAO was dead and 
ADO was the future but then reversed itself with Access 12.

2) ...see above

3) ...no, you can use DAO but it isn't as efficient ...what you can't do 
with DAO is use an ADP to connect to a SQL be ...but you can certainly 
connect ...I'd venture to guess there are still more Access fe's using DAO 
to connect to SQL be's just because for years that was the only way to do 
it.

...hth

William Hindman

----- Original Message ----- 
From: "Jim Hewson" <JHewson at karta.com>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Tuesday, May 15, 2007 10:18 AM
Subject: [AccessD] DAO vs ADO


> I'm confused when looking at these two libraries.  My questions are
> many, so I listed only a few below.
> 1.  What is the difference?  Yeah I know, this is a loaded question, but
> how do I know when looking at code it's either one?
> Can they be mixed?
>
> 2.  Which is recommended for MDBs - or is there no difference in
> performance?
>
> 3.  I read somewhere, that ADO is required for ODBC to SQL Server with
> an Access FE - is that correct?
>
> That's enough for now, Thanks!
>
> Jim
>
> Jim H. Hewson
> Applications Support Manager
> Karta Technologies, Inc.
> 5555 Northwest Parkway
> San Antonio, Texas 78249
> 210-582-3233
> jhewson at karta.com
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>