Stops asking "would you like to save your changes..."

[Bonnie]

Hi there! Using A02 in XP. This happens every few weeks
and when it does....ARGHHHH! I like Access to prompt me to
save or not to save when I'm doing any kind of design
work. I'll be working right along and try something in a
query that doesn't work or I get confused and I can do the
classic "close, don't save and reopen". I can't figure out
why but once in a while I'll close something and realize a
second later that IT JUST CLOSED! Don't ask, don't tell...

Messes me up BIG time. Systems has no clue. I reboot,
restart, shutdown, etc. and it keeps doing it until it
decides to stop. And at some point, usually overnight, it
prompts again.

Any ideas? Thanks in advance for any help or advice!

 

[Dirk Goldgar]

Hi there! Using A02 in XP. This happens every few weeks
and when it does....ARGHHHH! I like Access to prompt me to
save or not to save when I'm doing any kind of design
work. I'll be working right along and try something in a
query that doesn't work or I get confused and I can do the
classic "close, don't save and reopen". I can't figure out
why but once in a while I'll close something and realize a
second later that IT JUST CLOSED! Don't ask, don't tell...

Messes me up BIG time. Systems has no clue. I reboot,
restart, shutdown, etc. and it keeps doing it until it
decides to stop. And at some point, usually overnight, it
prompts again.

Any ideas? Thanks in advance for any help or advice!

It may be that somewhere your application there's code that executes
DoCmd.SetWarnings False (or a macro that executes the SetWarnings action
to turn off warnings) and then fails to turn it back on again. This
should not persist across an exit from Access, though, so I'm not sure
this is the cause of your problem. Maybe the intemittancy of it
reflects an error condition that may or may not occur, and that error is
preventing the code (which has previously turned warning off) from
reaching the step where warnings are turned back on again.

 

[Bonnie]

Hi Dirk,

Hmmmm. You may have something there. I do use some
SetWarnings.False in macros in my DB's. I need to test
that. I'll create a macro for true and run it next time
this happens. Great food for thought....Thx!