[AccessD] DoCmd.RunSQL or CurrentDb.Execute?

One more thing on this, if you want to be able to rollback your changes in a
workspace transaction, you need to run CurrentDb.Execute

Mark Whittinghill
Symphony Information Services
763-391-7400
mwhittinghill at symphonyinfo.com
----- Original Message ----- 
From: "Developer" <Developer at ultradnt.com>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Tuesday, January 06, 2004 4:42 PM
Subject: RE: [AccessD] DoCmd.RunSQL or CurrentDb.Execute?


> Currentdb.execute will bypass the warnings if they are on,
> Docmd will still have the warnings.
> Currentdb has been faster for me, but I havent benchmarked anything
> specific.
>
> Hth
> Steve
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Fenton
> Sent: Tuesday, January 06, 2004 5:22 PM
> To: accessd at databaseadvisors.com
> Subject: [AccessD] DoCmd.RunSQL or CurrentDb.Execute?
>
>
>
> Quick question...
> Which is better to use?
> Assuming an SQL string in a variable called strSQL
> Then...
>
> DoCmd.RunSQL strSQL
> Or
> CurrentDb.Execute strSQL
>
> They both have the same outcome; I was just wondering whether one was
> maybe faster or something?
>
> Cheers
> David
> Brisbane
> Australia
>
>
> _______________________________________________
> 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
>
>