Roger Carlson said:
You can either bracket it with the SetWarnings command:
DoCmd.SetWarnings False
DoCmd.RunSQL
DoCmd.SetWarnings True
But also make sure you put the DoCmd.SetWarnings True line in the
error handling or wield things will start happening in your app. Or
rather expected warnings won't pop up especially when developing.
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/