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

Only if you're working with multiple, but separate records -- that's what I 
read, I think. I'm not sure why that is though.

Susan H.


> So it would seem that DAO with the OpenRecordset outside the loop is the
> fastest?
>
>
> Rocky Smolin
> Beach Access Software
> 858-259-4334
> www.e-z-mrp.com
> www.bchacc.com
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Martin Reid
> Sent: Wednesday, October 29, 2008 7:09 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Which Is Faster - DAO or db.Execute?
>
> Susan
>
> You might find this useful
>
> http://www.tech-archive.net/Archive/Access/microsoft.public.access.modulesda
> ovba/2005-03/1330.html
>
> Martin
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
> Sent: 29 October 2008 14:00
> 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
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com