Access 97 - Turn of Access Warnings

[PMB]

Thank you in advance for any and all assistance.

I'm running Queries for updating my forms and I want to turn off the
Internal Warnings that access gives.

How do I do that?

Michael

[Allen Browne]

Re: Access 97 - Turn of Access Warnings

Not exactly clear what you are doing, but you could try one of these:

1. Turn SetWarnings off.

2. Change the settings under Tools | Options | Edit/Find | Confirm.

3. dbEngine(0)(0). Execute "MyQuery"

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html

"PMB" <pmbragg@megavi sion.com> wrote in message
news:KJxfb.6$8q 2.2696@news.usw est.net...[color=blue]
> Thank you in advance for any and all assistance.
>
> I'm running Queries for updating my forms and I want to turn off the
> Internal Warnings that access gives.
>
> How do I do that?
>
> Michael
>
>[/color]

[Saintor]

Re: Access 97 - Turn of Access Warnings

In code...
Docmd.setwarnin gs true or false

"PMB" <pmbragg@megavi sion.com> wrote in message
news:KJxfb.6$8q 2.2696@news.usw est.net...[color=blue]
> Thank you in advance for any and all assistance.
>
> I'm running Queries for updating my forms and I want to turn off the
> Internal Warnings that access gives.
>
> How do I do that?
>
> Michael
>
>[/color]

[Pieter Linden]

Re: Access 97 - Turn of Access Warnings

"PMB" <pmbragg@megavi sion.com> wrote in message news:<KJxfb.6$8 q2.2696@news.us west.net>...[color=blue]
> Thank you in advance for any and all assistance.
>
> I'm running Queries for updating my forms and I want to turn off the
> Internal Warnings that access gives.
>
> How do I do that?
>
> Michael[/color]

DoCmd.SetWarnin gs False
DoCmd.OpenQuery "qupdWhatev er"
DoCmd.SetWarnin gs True

On Error
DoCmd.SetWarnin gs True

[Tony Toews]

Re: Access 97 - Turn of Access Warnings

"PMB" <pmbragg@megavi sion.com> wrote:
[color=blue]
>I'm running Queries for updating my forms and I want to turn off the
>Internal Warnings that access gives.[/color]

I prefer, if DAO, to use Currentdb.Execu te strSQL,dbfailon error command instead of
docmd.runsql. For ADO use CurrentProject. Connection.Exec ute strCommand,
lngRecordsAffec ted, adCmdText

If you're going to use docmd.setwarnin gs 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.execu te 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