Re: Access 2000 Make Table Query Warning Box -- use currentdb.exec

Thanks Crystal. Sorry - definitely non-programmer at the other end of this
email discussion..... Where should I put this? and how?

Am I putting it at the beginning of the query code? or somewhere else so
that it effects the entire database? I have managed to build without using
SQL so far and messing around in the code makes me squeamish to say the least.

Thanks again.

Jennifer

"strive4peace" <"strive4peace2006 at yaho" wrote:

Hi Jennifer

instead of using DoCmd, use this form

currentdb.execute "SQL or action queryname"

this operates as
docmd.echo false
docmd.setwarnings false
docmd.openquery qname
docmd.echo whatever it was
docmd.setwarnings whatever it was


Warm Regards,
Crystal
Microsoft Access MVP 2006

*
Have an awesome day ;)

remote programming and training
strive4peace2006 at yahoo.com

*

ProCad Jen wrote:
I am using Access 2000. I love this program, except.....

I have create a couple of make table queries which ask for input from the
user. When this query is run, and before it asks the user for the input, I
get a warning message that says that the query is about to replace the table
with new data, and is the user ok with that?, yes or no. As the database
designer, I know to answer yes, and it goes through the function with no
issues.

I don't WANT the warnings to show up, so I went into the
Tools>Options>Edit/Find and cleared the "Action Queries" box under the
confirm section. I have applied it. I have ok'd it. I have done this on
every possible table, query, form etc. that is involved with these two
queries. (not that it is a different menu with each one, but I was grasping
at straws.) I have restarted the program multiple times. I have rebooted
the computer multiple times.

The check boxes are EMPTY, but the warnings keep coming up. Is this a
problem with Access? or am I missing something. I will be authorizing
non-Access users to enter data into this database; I have been working on
this massive user-friendly, smooth-flowing database for almost two months,
and I don't want to have to say "just answer "yes" to the warning - I can't
make them go away."

If anyone knows of a fix, or SOMETHING to make these things go away, please
share!!!

Jennifer


.

Relevant Pages

  • Re: changed queries save automatically
    ... Check out Allen Browne's "bug" about Name AutoCorrect. ... A query not prompting you about saving it is one of the symptoms of this ... Either something else is turning off warnings or we're dealing with a bug ... Compacting and repairing closes the database and reopens it. ...
    (microsoft.public.access.queries)
  • Re: changed queries save automatically
    ... Not exactly a "tiny" bug is it? ... A query not prompting you about saving it is one of the symptoms of this ... macro or code someone has Set Warnings to Off but forgot to Set ... Compacting and repairing closes the database and reopens it. ...
    (microsoft.public.access.queries)
  • Re: Query Data on a Form
    ... What do you mean you will need to enter it multiple times due to another ... If you need to export it to another database with the address ... then Crete a query that will show the address for each record. ... Rick B ...
    (microsoft.public.access.forms)
  • Re: changed queries save automatically
    ... MS is very aware of this bug, and it's been looked at in many ... Just today I create a new query in A03 ... macro or code someone has Set Warnings to Off but forgot to Set ... Compacting and repairing closes the database and reopens it. ...
    (microsoft.public.access.queries)
  • Re: Running queries with VBA functions in external database
    ... Originally I was running without setting the warnings off ... to execute DoCmd.OpenQuery actionQueryName in the same ... database - it comes up with a confirmation, ... >> I have an query that utilizes my Custom VBA ...
    (microsoft.public.access.modulesdaovba)