set warnings is disabling my code

[theintern]

I had a macro, with a SetWarnings command in it. it worked great. i
converted it vba. it didn't work. but, as soon as i comment out
DoCmd.SetWarnings False and click my way through it, it works great. what is
going on? i need it to not show the warnings and just continue, as it did
when it was a macro.

thanks
scott

 

[ruralguy via AccessMonster.com]

Did the code turn Warning back on at the end? What do you mean "it didn't
work"? Did it do anything? What code was generated? Can you post it?

 

[Tony Toews [MVP]]

I had a macro, with a SetWarnings command in it. it worked great. i
converted it vba. it didn't work. but, as soon as i comment out
DoCmd.SetWarnings False and click my way through it, it works great. what is
going on? i need it to not show the warnings and just continue, as it did
when it was a macro.

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/