Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Queries / August 2006

Tip: Looking for answers? Try searching our database.

How to hide the message box when making a table?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jesZee - 09 Aug 2006 21:19 GMT
Hi Access-guru,

I have a macro that make & append data to a table. However, each time I
ran it, there will be messages popping up telling me that the old table
will be deleted and I will append # of data into my new table. I want
to suppress that comment but can't seem to make it work.

I have tried putting in "Echo" before the "Make table" in the Action
field and after the Make table - but nothing works.

Please assist.

THANK YOU VERY MUCH.

J.
Jerry Whittle - 09 Aug 2006 21:54 GMT
Instead of Echo use SetWarnings Off.

Before the maco ends SetWarnings back to On or you will eventually regret it.
Signature

Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

> Hi Access-guru,
>
[quoted text clipped - 11 lines]
>
> J.
Armen Stein - 09 Aug 2006 22:08 GMT
> Hi Access-guru,
>
[quoted text clipped - 11 lines]
>
> J.

Try setting SetWarnings to No.

Remember to turn it back to Yes when you're done - it persists for the
duration of your Access session otherwise.

Signature

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

John Vinson - 09 Aug 2006 22:11 GMT
>Hi Access-guru,
>
[quoted text clipped - 11 lines]
>
>J.

Right before you run the query, set SetWarnings to False; be sure to
set SetWarnings to True on the line after, or you'll turn off ALL
warning messages.

Or, run the query in VBA code using the Querydef Execute method
instead of using macros. This will let you trap actual query errors
(which the macro cannot do).

                 John W. Vinson[MVP]
jesZee - 14 Aug 2006 19:34 GMT
Thanks John and everyone....you guys have been of great help.

j.

> >Hi Access-guru,
> >
[quoted text clipped - 21 lines]
>
>                   John W. Vinson[MVP]
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.