changed queries save automatically

[Guest]

I am working in Access 2003 SP2 and I have to continually Compact and Repair
the database, because I do not always get the popup asking if I want to save
a changed query. I like to open an existing query and do a “What If†change,
but don't want to have that change saved when I close the query. Sometimes I
can work in the database for a while before it saves changes automatically.
Has anyone else run into this problem.

 

[Darren]

I have seen this in Access 200 as well. It will also get to a point where it
won't let me close a new query without saving it.

 

[Guest]

Yes I have and it's not what you think such as corruption. Most likely in a
macro or code someone has Set Warnings to Off but forgot to Set Warnings back
on when finished. Often people turn the warnings off when doing something
like automatically appending a lot of data or deleting records so that they
don't get bugged with all the "do you really want to" messages.

Compacting and repairing closes the database and reopens it. By default when
the database opens, Set Warning is on until someone turns it off. You might
even have something running from the startup form or the autoexec macro that
turns off the warnings.

If I'm right (it's been known to happen) about the time that your changed
queries save without asking, you'll also find that changed forms and reports
will do the same thing. Even closing the database and reopening should fix it
unless it's a startup form or autoexec macro kicking in.

 

[Guest]

By Geroge I think that did it! Thanks!

Yes I have and it's not what you think such as corruption. Most likely in a
macro or code someone has Set Warnings to Off but forgot to Set Warnings back
on when finished. Often people turn the warnings off when doing something
like automatically appending a lot of data or deleting records so that they
don't get bugged with all the "do you really want to" messages.

Compacting and repairing closes the database and reopens it. By default when
the database opens, Set Warning is on until someone turns it off. You might
even have something running from the startup form or the autoexec macro that
turns off the warnings.

If I'm right (it's been known to happen) about the time that your changed
queries save without asking, you'll also find that changed forms and reports
will do the same thing. Even closing the database and reopening should fix it
unless it's a startup form or autoexec macro kicking in.

 

[Don Small]

Hi Jerry,

I have been researching this thread topic in both the general access and
access.queries groups. Although your logic seems correct, I have had this
problem show up in mutliple databases and I never have used the SetWarnings
command and always have the option "Confrm Action Queries" checked on. In
fact, when I observe this behavior I have checked the "Confrm Action
Queries" and it still shows checkd on.

Either something else is turning off warnings or we're dealing with a bug
(that wouldn't be a first). BTW - I never experienced this before Access
2003 and have used Access since Office 95.

Any more thoughts?

Don Small

 

[Guest]

Hi Don,

I've never seen this behavior. Just today I create a new query in A03 and
was prompted to save after closing. Then I modified another query and was
also prompted to save it.

If a program does something that is not expected; is intermittent; and no
reasonable explaination, I think that fits the definition of a bug.

 

[Ken Snell \(MVP\)]

Check out Allen Browne's "bug" about Name AutoCorrect.
http://allenbrowne.com/bug-03.html

A query not prompting you about saving it is one of the symptoms of this
"tiny", irritating bug.

 

[Don Small]

Good grief! Not exactly a "tiny" bug is it?

Thanks Ken - this is great advice and very likely what is causing this and
other problems. Leave it to Microsoft to have so many known bugs that
aren't fixed... It's very unprofessional of Microsoft to leave known issues
uncorrected if you ask me.

Thanks again to you and Jerry for your help. I just joined MS Usergroups
yesterday and am very please with this excellent community forum.

Don

 

[Ken Snell \(MVP\)]

Some bugs are difficult to fix because they will break other things when
fixed.... MS is very aware of this bug, and it's been looked at in many
ways... I think the new ACCESS 2007 version will show some improvements, but
one never knows until it's released.