[AccessD] Which Is Faster - DAO or db.Execute?

Jim Dettman jimdettman at verizon.net
Wed Oct 29 09:54:19 CDT 2008


Susan,

<< My claim is that SQL is faster -- it speaks directly to the engine>>

  So does DAO.  In fact unlike SQL, it doesn't need to be parsed and have a
costing plan generated.  

<<-- it has to be faster.>>

  I think you'd need to test to be sure.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Wednesday, October 29, 2008 10:00 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Which Is Faster - DAO or db.Execute?

>
>  Both are DAO, but what he is asking is if db.Execute with a SQL statement
> is faster then opening up a record set, finding the record, and then doing
> an .Edit/.Update.

======Yes, I realize they're both DAO, I just thought I'd clarify. My claim 
is that SQL is faster -- it speaks directly to the engine -- it has to be 
faster.

SUsan H.


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list