Access 2003 doesn't warn to save changes any more

[M Skabialka]

An Access 2003 database which I have been using for a couple of years,
making changes fairly often, has suddenly stopped asking me if I want to
save changes I have made to forms, queries etc when I close them. I used
the code editor, immediate window to 'docmd.setwarnings true', but it still
accepts all changes without question. I shut down and restarted the
database, compacted and recompiled it.
Is there another setting which may have been inadvertantly changed?
Thanks,
Mich

 

[Arvin Meyer [MVP]]

An Access 2003 database which I have been using for a couple of years,
making changes fairly often, has suddenly stopped asking me if I want to
save changes I have made to forms, queries etc when I close them. I used
the code editor, immediate window to 'docmd.setwarnings true', but it
still accepts all changes without question. I shut down and restarted the
database, compacted and recompiled it.
Is there another setting which may have been inadvertantly changed?

Saving 1 thing, saves everything, and certain form changes, like filters,
haven't induced a prompt since Access 97.

I've never seen a code change that didn't offer a prompt. I'm not sure
what's happened to your installation, but you might try using Saves As from
the file menu, just before closing and see if that helps.

 

[M Skabialka]

It's the inadvertent changes that worry me - if I am looking at a form and
accidentally move something, or change a control source query and don't get
a warning when I close the form as I should do, so I can say 'Don't save
changes' because nothing was intentional...

 

[M Skabialka]

I did a decompile and recompile and now I am getting my Save prompts. But I
wonder what underlying feature is lurking in the background that caused the
problem - scary - as this has to go back into production.

 

[Maurice]

Have you looked at your code and checked all the DoCmd.SetWarnings settings
which you might use? Make sure that you always put the DoCmd.SetWarnings back
to true in your error handling. Maybe some code isn't executed correctly and
by not setting the docmd back to true you might run into situations like this.

So check every docmd both ways (False - True) also in the error handler of
the sub you are using it in.

And a second long shot you could look at is under the Tools-options and look
for the tab where you can check the option to surpress warnings for queries
etc. Maybe it's been unchecked by accident.

hth