Update Query Warning Message

[John W]

I have a macro that will import a series of text files and then perform some
Delete Queries...how can I stop the warning box that comes up and notifies
you that you are about to delete records from your table?

Thanks!

 

[fredg]

I have a macro that will import a series of text files and then perform some
Delete Queries...how can I stop the warning box that comes up and notifies
you that you are about to delete records from your table?

Thanks!

Using Macro's?

Macro SetWarnings False
Macro Run Query "Delete Query Name"
Macro SetWarnings True

Using code, it would be:

DoCmd.SetWarnings False
DoCmd.OpenQuery "QueryName"
DoCmd.SetWarnings True

 

[Guest]

There are a couple of ways you can do this.

Calling the queries by using CurrentDb.Execute will work as well as using

DoCmd.SetWarnings False
...do your queries
DoCmd.SetWarnings True

but if you do that, be sure to have an error handler and put the
DoCmd.SetWarnings True in the first line of your error handler or else you
might find yourself without warnings at all.

 

[John W]

Thanks - I knew it had to be simple!

Using Macro's?

Macro SetWarnings False
Macro Run Query "Delete Query Name"
Macro SetWarnings True

Using code, it would be:

DoCmd.SetWarnings False
DoCmd.OpenQuery "QueryName"
DoCmd.SetWarnings True

 

[Tony Toews [MVP]]

I have a macro that will import a series of text files and then perform some
Delete Queries...how can I stop the warning box that comes up and notifies
you that you are about to delete records from your table?

Don't use Setwarnings, it's too dangerous.

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/