I just installed MS Access 2007. Is there any way to turn off the
confirmation of action queries in 2007 ?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-ac cess/200712/1

On Sun, 23 Dec 2007 17:46:12 GMT, "destinman via AccessMonster.com"
<u18648 [at] uwe> wrote:

Check out:
DoCmd.SetWarnings

-Tom.


>I just installed MS Access 2007. Is there any way to turn off the
>confirmation of action queries in 2007 ?

On Dec 23, 7:02=A0pm, Tom van Stiphout <no.spam.tom7... [at] cox.net> wrote:
> On Sun, 23 Dec 2007 17:46:12 GMT, "destinman via AccessMonster.com"
>
> <u18648 [at] uwe> wrote:
>
> Check out:
> DoCmd.SetWarnings
>
> -Tom.
>
>
>
> >I just installed MS Access 2007. =A0Is there any way to turn off the
> >confirmation of action queries in 2007 ?- Hide quoted text -
>
> - Show quoted text -

Offioce Button > Access Options > Advanced > Untick "Confirm Action
Queries"

"destinman via AccessMonster.com" <u18648 [at] uwe> wrote:

>I just installed MS Access 2007. Is there any way to turn off the
>confirmation of action queries in 2007 ?

Inside macros or code?

If VBA code I prefer, if DAO, to use Currentdb.Execute strSQL,dbfailonerror command
instead of docmd.runsql. For ADO use CurrentProject.Connection.Execute strCommand,
lngRecordsAffected, adCmdText

If you're going to use docmd.setwarnings make very sure you put the True statement in
any error handling code as well. Otherwise weird things may happen later on
especially while you are working on the app. For example you will no longer get the
"Do you wish to save your changes" message if you close an object. This may mean
that unwanted changes, deletions or additions will be saved to your MDB.

Also performance can be significantly different between the two methods. One posting
stated currentdb.execute took two seconds while docmd.runsql took eight seconds. As
always YMMV.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

For more info on Tony's suggestion, see:
Action queries: suppressing dialogs, while knowing results
at:
http://allenbrowne.com/ser-60.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tony Toews [MVP]" <ttoews [at] telusplanet.net> wrote in message
news:tsvtm3la0ebkf8dvbrk383o4bdb91cpgqg [at] 4ax.com...
> "destinman via AccessMonster.com" <u18648 [at] uwe> wrote:
>
>>I just installed MS Access 2007. Is there any way to turn off the
>>confirmation of action queries in 2007 ?
>
> Inside macros or code?
>
> If VBA code I prefer, if DAO, to use Currentdb.Execute
> strSQL,dbfailonerror command
> instead of docmd.runsql. For ADO use CurrentProject.Connection.Execute
> strCommand,
> lngRecordsAffected, adCmdText
>
> If you're going to use docmd.setwarnings make very sure you put the True
> statement in
> any error handling code as well. Otherwise weird things may happen later
> on
> especially while you are working on the app. For example you will no
> longer get the
> "Do you wish to save your changes" message if you close an object. This
> may mean
> that unwanted changes, deletions or additions will be saved to your MDB.
>
> Also performance can be significantly different between the two methods.
> One posting
> stated currentdb.execute took two seconds while docmd.runsql took eight
> seconds. As
> always YMMV.
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/