confirmation messages in Access 2007 NikkiV 12/31/2008 2:31:01 PM Please could anyone tell me how to turn off confirmation messages. In Access 2003 it was Tools/Options/EditFind etc ... but I can't find the equivalent in Access 2007 Help!! Nikki

RE: confirmation messages in Access 2007 MikeJohnB 12/31/2008 2:46:01 PM In Access 2007, most of the options which were available in Access 2003 are still available in the database but are arrived at by clicking the windows globe at the top left hand side of the database. Select Access Options from the bottom of the popup menu, take a look at advanced group I think it is. Howevere there are several options available in the various groups. I hope this helps Kindest regards Mike B Happy 2009 -- Advice to Posters. Check your post for replies or request for more information. Consider providing some feed back to the response you have recieved. Kindest Regards Mike B "NikkiV" wrote: [Quoted Text] > Please could anyone tell me how to turn off confirmation messages. In Access > 2003 it was Tools/Options/EditFind etc ... but I can't find the equivalent in > Access 2007 > > Help!! > > Nikki

Re: confirmation messages in Access 2007 "Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> 1/1/2009 1:17:19 AM NikkiV <NikkiV[ at ]discussions.microsoft.com> wrote: [Quoted Text] >Please could anyone tell me how to turn off confirmation messages. In Access >2003 it was Tools/Options/EditFind etc ... but I can't find the equivalent in >Access 2007 Why would you want to? If you mean confirmation messages caused by DoCmd.RunSQL then don't use it. The problem with DoCmd.RunSQL is that it ignores any errors. Either of the following will display any error messages received by the query. If using DAO, use Currentdb.Execute strSQL,dbfailonerror.. For ADO use CurrentProject.Connection.Execute strCommand, lngRecordsAffected, adCmdText You can then remove the docmd.setwarnings lines. 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/