Turn confirmation messages on or off

[David Kennedy]

Hi ,

I was wondering if anyone knows how to turn confirmation messages on or off
in Access 2007.?

In access 2000, I know how to do it through code(DoCmd.SetWarnings = False)
and menu (Tools->Options->Edit/Find Tab->Confirm.....)

But how do I turn these messages on/off using the menus in Access 2007?

Thanks in advance,
DK

 

[Allen Browne]

Go to:
- Office Button (top left)
- Access Options (bottom of dialog)
- Advanced (left pane)
- Confirm (under Editing)

BTW, MS has a screen to help you find where things have gone:
http://office.microsoft.com/en-us/access/HA102388991033.aspx

If you were already familiar with the old versions, this might help:
Converting to Access 2007
at:
http://allenbrowne.com/Access2007.html

 

[David Kennedy]

Thanks Allen

Go to:
- Office Button (top left)
- Access Options (bottom of dialog)
- Advanced (left pane)
- Confirm (under Editing)

BTW, MS has a screen to help you find where things have gone:
http://office.microsoft.com/en-us/access/HA102388991033.aspx

If you were already familiar with the old versions, this might help:
Converting to Access 2007
at:
http://allenbrowne.com/Access2007.html

 

[Tony Toews [MVP]]

In access 2000, I know how to do it through code(DoCmd.SetWarnings = False)
and menu (Tools->Options->Edit/Find Tab->Confirm.....)

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/