Edward S Zuris
edzedz at comcast.net
Wed Oct 29 09:38:22 CDT 2008
Here is something to try. You can put various operations inside a for-next loop and collect times just before the start and after. Then calculate which is the faster with your VBA coding style implementations. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Dettman Sent: Wednesday, October 29, 2008 6:22 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Which Is Faster - DAO or db.Execute? Susan, 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. I think the only way you'd know for sure to time each, but I'm sure a .Seek on the index would beat either. Especially if you do more then one. And if more then one was being done at a time, I believe the record set method would be faster even with using a FindFirst, although I could be wrong on that. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Tuesday, October 28, 2008 11:46 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Which Is Faster - DAO or db.Execute? I'm not sure exactly what you're asking -- are you asking which is faster, ADO or SQL? Susan H. > Stuart: > > Gotta do each one separately since the user may select certain lines from > a > timesheet to bill and leave others for later. -- 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