By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,963 Members | 1,902 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,963 IT Pros & Developers. It's quick & easy.

Eliminating warning messages

P: n/a
Hi:

I have W98 and Access 2000, and am running a fairly complex application with all sorts of
delete and append queries. These queries run in background on my system, and make no fuss
when they execute. I am now moving the application to another system which has Windows XP
(Home) and Access 2003 (or possibly 2002). When it runs on the new system all sorts of
irritating warnings pop up (delete queries for example) and interrupt the whole process.
How do I switch these OFF? I cant find the settings to do this.

Thanks

John Baker
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
John Baker <Ba******@Verizon.net> wrote:
I have W98 and Access 2000, and am running a fairly complex application with all sorts of
delete and append queries. These queries run in background on my system, and make no fuss
when they execute. I am now moving the application to another system which has Windows XP
(Home) and Access 2003 (or possibly 2002). When it runs on the new system all sorts of
irritating warnings pop up (delete queries for example) and interrupt the whole process.
How do I switch these OFF? I cant find the settings to do this.


These are somewhere in the Tools >> Options possibly Edit/Find at least in A97. But
this is not your best place to make this change. This is the quick and dirty fix.
Standard blurb follows:

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 wierd 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
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.