Is there away to bypass the messageboxes on query tables?

[ryan.fitzpatrick3]

I have a query that I want turned into a table query. Is there away to
turn off the prompts saying do you want to post #,### records and just
do it. I'd like to make a macro do run this at night, but the prompts
are making that not happen for me.

 

[Arvin Meyer [MVP]]

Use VBA code. It can be as simple as:

Sub Form_Open()
DoCmd SetWarnings False
DoCmd.OpenQuery "YourQuery"
DoCmd SetWarnings True
End Sub

 

[Tony Toews [MVP]]

I have a query that I want turned into a table query. Is there away to
turn off the prompts saying do you want to post #,### records and just
do it. I'd like to make a macro do run this at night, but the prompts
are making that not happen for me.

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/