View Single Post
  #4 (permalink)  
Old December 12th, 2006, 08:54 AM
FalseParadigm FalseParadigm is offline
Authorized User
 
Join Date: Dec 2006
Location: Florence, KY, USA.
Posts: 18
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via AIM to FalseParadigm
Default

Quote:
quote:Originally posted by AccessMaster
 It is also possible to use:

Docmd.SetWarning = False

Docmd.OpenQuery ...
DoCmd.RunSQL ...

Docmd.SetWarning = True


Be sure that you remember to set the warning back on.

Boyd
"Hi Tech Coach"
Access Based Accounting/Business Solutions developer.
http://www.officeprogramming.com
Thank you for your help. Just as a clarification for users that might be working in Access 2003 (I know I didn't specify in the OP - that's my bad).

The proper syntax for warnings in Access 2003 is:

DoCmd.SetWarnings (0) 'For off
DoCmd.SetWarnings (1) 'For on

Again, thanks for your help, everything works as expected now. Now I just have to get over the feeling that I should have known this going in.

--------------------------------
"It's my way, or the Hemingway."
--------------------------------
Reply With Quote