*HELP* disabling annoying pop ups

[Bob Quintal]

=?Utf-8?B?S2FzZWFubw==?= <[email protected]>
wrote in

I have two examples that I would LOVE to get rid of if it's at
all possible.

1
the 3 pop-ups when you start access. I'm guessing those can't
be removed because they "protect" your computer.

These can be removed by setting securityaccess to low, but your
sysadmin will not like that.

2
When access is used from a different computer, SQLs run
through VB will prompt message boxes asking whether you want
to, "are you sure you want to ..."
"update these fields"
"add new data"
"delete this or that"
etc

I was wondering if there was a way to shut that off?

Yes, either by setting the Tools->Options->Edit/Find->Confirm->
record changes to unchecked, or by putting docmd.setwarnings off
before, and docmd.setwarnings on after, each command that
generates these almost useless messages.

Be careful though. The messages are sometimes useful, so don't
just turn them off and leave them off.

Thanks so much for any help.

 

[Guest]

I have two examples that I would LOVE to get rid of if it's at all possible.

1
the 3 pop-ups when you start access. I'm guessing those can't be removed
because they "protect" your computer.

2
When access is used from a different computer, SQLs run through VB will
prompt message boxes asking whether you want to,
"are you sure you want to ..."
"update these fields"
"add new data"
"delete this or that"
etc

I was wondering if there was a way to shut that off?

Thanks so much for any help.

 

[Tony Vrolyk]

For the second point you can run the SQL with a different method by using a
db.execute. This does not create warnings so you can safely leave SetWarning
alone. I use something like the following.

dim db as database, strSql as string
set db = currentdb()
strsql = "something"

db.execute strSql, dbfailonerror

db.close
set db = nothing


Plus if you do use docmd.setwarnings and then there is an error in the code
which is not properly handled then you end up with warnings being off which
could cause a problem.

Tony

 

[Guest]

I'll switch them all over thanks a lot.

Just wondering what dbFailOnError does btw?

For the second point you can run the SQL with a different method by using a
db.execute. This does not create warnings so you can safely leave SetWarning
alone. I use something like the following.

dim db as database, strSql as string
set db = currentdb()
strsql = "something"

db.execute strSql, dbfailonerror

db.close
set db = nothing


Plus if you do use docmd.setwarnings and then there is an error in the code
which is not properly handled then you end up with warnings being off which
could cause a problem.

Tony