Edward S Zuris
edzedz at comcast.net
Wed Oct 29 09:18:56 CDT 2008
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 Rocky Smolin at Beach Access Software Sent: Tuesday, October 28, 2008 9:23 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Which Is Faster - DAO or db.Execute? Db.Execute "Update..." vs. DAO. 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 Susan Harkins Sent: Tuesday, October 28, 2008 8: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