Not Enough Memory to Undo -Suppress

[Guest]

We want a process to run completely through without having to monitor. We
keep getting the prompt "Not enough memory to undo" I set warnings = false;
but we are still getting this message. Any idea on how to suppress all
messages?

Thanks, Charles

 

[Tony Toews]

We want a process to run completely through without having to monitor. We
keep getting the prompt "Not enough memory to undo" I set warnings = false;
but we are still getting this message. Any idea on how to suppress all
messages?

Is this process in VBA code? Presumably these are queries? Are you
using docmd.runsql or execute for the queries?

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

 

[Guest]

Is this process in VBA code? Presumably these are queries? Are you

using docmd.runsql or execute for the queries?

Tony

Presently we are run a series of 22 queries from a macrogroup. As soon as
everything looks all right we will put it in VBA code. So VBA code to supress
would be great.

 

[Tony Toews]

Presently we are run a series of 22 queries from a macrogroup. As soon as
everything looks all right we will put it in VBA code. So VBA code to supress
would be great.

And these are action queries? Standard blurb follows on Setwarnings.

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