M
mscertified
What is the difference between (and is either preferred):
Docmd.RunSQL "SQL statement"
and
CurrentProject.Connection.Execute "SQL statement"
Docmd.RunSQL "SQL statement"
and
CurrentProject.Connection.Execute "SQL statement"
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
John W. Vinson
What is the difference between (and is either preferred):
Docmd.RunSQL "SQL statement"
and
CurrentProject.Connection.Execute "SQL statement"
One big difference is that the former does not let you trap errors, and the
latter does.
D
Dale Fye
It's been so long since I've used RunSQL.
Doesn't it require SetWarning Off/On to prevent warnings as well?
--
Don''t forget to rate the post if it was helpful!
email address is invalid
Please reply to newsgroup only.
Doesn't it require SetWarning Off/On to prevent warnings as well?
--
Don''t forget to rate the post if it was helpful!
email address is invalid
Please reply to newsgroup only.
J
John W. Vinson
It's been so long since I've used RunSQL.
Doesn't it require SetWarning Off/On to prevent warnings as well?
Yep - that's another of its disadvantages vis a vis the Execute method.
M
mscertified
And the .execute method allows you to get the 'records affected' count back -
which is sometimes very useful.
which is sometimes very useful.
A
Allen Browne
mscertified said:What is the difference between (and is either preferred):
Docmd.RunSQL "SQL statement"
and
CurrentProject.Connection.Execute "SQL statement"
Differences explained here:
Action queries: suppressing dialogs, while knowing results
at:
http://allenbrowne.com/ser-60.html