RunSQL Macro Command

[JDubya]

Hi All, I currently have a macro, that using the OpenQuery macro action, runs a number of update queries. However, as my database expands I do not want endless queries clogging up the navigation pane, so after finding out about the RunSQL macro command, I wish to copy the SQL statement for each query and store it in the related macro and then delete the original query. However, I'm a bit confused by the Use Transaction argument of the RunSQL command. Access Help tells me that I am supposed to set this argument to YES if I wish to include the query in a transaction, but what does Access mean by a transaction. Surely just running the query is a transaction of sorts?? Can anybody explain this to me as Help goes on to say that by setting the argument to No means the query may run faster, so it would be useful if I had confidence in knowing what to select for this argument and in what situation.

Many thanks
John

 

[CJ_London]

I don't use macros, so I'm guessing transactions is the equivalent to the vba begintrans and commitrans functions - google to find the detail but in principle it allows all query transactions to be rolled back if one of them fails

 

[JDubya]

Oh I see, thanks for the explanation Cj and to be honest I didn't even know that Access could do that. As for Macros, yeah although I did a bit of work with Access back in 2007 I haven't touched it since, so as I'm starting to use it again I wanted to get a feel of it's basic objects first before I really get my nose into learning VBA and really feeling the power! Anyway, many thanks CJ for your help.
Cheers
John