Comparison of runSQL and Qry.Execute

[jaydwest]

Does anyone have a comparison of runSQL and qry.Execute to execute an action query. Specifically would like to know

1) Does either run faster
2) Does either generate less overhead, e.g. running an unnamed query should not add to database disk space. Is this true with RunSQL too?
3) Any other comparisons?

Thanks

 

[PaulSpell]

Pat,

OK, but if your action query needs to be programatically re-created each time it is run (for example if field names or values need to be dynamically changed) then there is presumably no overhead in using runsql as opposed to saving the querydef and then running it?