no longer prompted to save, saves automatically-not desired

[Guest]

Today, for no apparent reason, when I change something (table, form, report)
and then close it, I don't get the "do you want to save prompt". I have not
knowingly turned this off and I don't know how to turn it back on.
I do want this option on because I don't want changes automatically saved.
Please advise.

 

[Paul Shapiro]

I've seen this behavior when I open a 2nd Access database programmatically
from VBA code in a 1st database. If you're not already opening Access
without any database first and then opening your db from within Access, you
could try that.
Paul Shapiro

 

[Guest]

Paul,
Thanks for your reply. That unfortunately did not have any effect, although
I have been doing alot of stuff in the VBA window today.

 

[Guest]

I still don't have an explanation for it, but it did not persist after I
restarted my computer. (Closing the database and Access 2007, and restarting
the application and DB alone did not fix the problem). It required me to
restart the computer.

 

[Dirk Goldgar]

In

Today, for no apparent reason, when I change something (table, form,
report) and then close it, I don't get the "do you want to save
prompt". I have not knowingly turned this off and I don't know how to
turn it back on.
I do want this option on because I don't want changes automatically
saved. Please advise.

One common cause of this is having code in your application that turns
off warnings with

DoCmd.SetWarnings False

without ensuring that, no matter what happens, you subsequently execute
a statement to turn warnings back on again:

DoCmd.SetWarnings True

For example, if a run-time error occurs after you have turned off
warnings, you need to make sure you have error-handling in place that
executes the statement to turn warnings back on.

 

[Guest]

Dirk,
Thanks for your reply. I did have some code to that effect which I did "turn
back on". I had actually "turned it off" a few days ago though and had been
working in the application alot before this occurred. I do think it may have
had some effect though.

 

[Pat Hartman \(MVP\)]

I occasionally turn off warnings in code using this message but when I do
that, I also turn the hourglass on as a visual reminder that warnings are
off. When I turn the warnings back on, I turn the hourglass off. I created
macros to do the two settings. That way, if I find my program has missed
the "on" part of the code, I can manually turn the warnings back on by
running the warningsOn macro. And then I fix the code.

As you have noticed, having warnings off when you are developing is VERY
dangerous.