Update query notifications

[Guest]

Hi all,
Can anyone tell me how to get rid of the annoying messages that pop up from
within Access when attempting to run an update or delete query? I would like
to have the ability to bypass those messages. Thank you in advance.

 

[strive4peace]

Hi John,

if you are using code to execute the query, use

currentdb.execute "QueryName"

instead of

DoCmd.OpenQuery "QueryName"

~~~~~~~~~~~~~~~~~~~~~~~~~

if you are using macros or just opening queries from the database
window, before you run action queries:

macro action --> SetWarnings --> false
macro action --> Echo --> false

then, after you run action queries...

macro action --> Echo --> true
macro action --> SetWarnings --> true

Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote programming and Training
strive4peace2006 at yahoo.com
*

 

[Guest]

NICE!
Thank you so very much.

Hi John,

if you are using code to execute the query, use

currentdb.execute "QueryName"

instead of

DoCmd.OpenQuery "QueryName"

~~~~~~~~~~~~~~~~~~~~~~~~~

if you are using macros or just opening queries from the database
window, before you run action queries:

macro action --> SetWarnings --> false
macro action --> Echo --> false

then, after you run action queries...

macro action --> Echo --> true
macro action --> SetWarnings --> true

Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote programming and Training
strive4peace2006 at yahoo.com
*

 

[Allen Browne]

Crystal has already answered your question, but if you want more detail see:
Action queries: suppressing dialogs, while knowing results
at:
http://allenbrowne.com/ser-60.html

 

[strive4peace]

You're welcome, John happy to help

Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote programming and Training
strive4peace2006 at yahoo.com
*

 

[strive4peace]

nice link, thanks Allen!

Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote programming and Training
strive4peace2006 at yahoo.com
*

 

[Tony Toews]

if you are using code to execute the query, use
currentdb.execute "QueryName"

Currentedb.execute "QueryName", dbfailonerrors is highly recommended
so you see any error messages.

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

 

[strive4peace]

thanks, Tony!

sometimes I leave off parameters to keep it simple, but using
dbFailOnError is a good idea ... especially if there is no error handler

Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote programming and Training
strive4peace2006 at yahoo.com
*

 

[Guest]

Thanks to Crystal, Allen and Tony for some excellent information. You guys
are great.

 

[strive4peace]

you're welcome, John happy to help

Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote programming and Training
strive4peace2006 at yahoo.com
*