Warnings/Saving Disabled? Other odd occurances...

[isoquin]

I've done my homework on this a bit already.

Problem: the usual warnings of "Do you want to save?" or "Are you sure you want to delete that? It cannot be undeleted." etc have mysteriously stopped working.

Tools > Options > Edit/Find > Confirm: all boxes are checked
DoCmd.SetWarnings is not ANYWHERE in ANY code of mine. Nonetheless, I threw it in once and set it to TRUE just to be safe. This did not remedy the problem.

This isn't the first bizarre case that's come up. I've had forms just completely die on me. My homework indicated it was "corrupt" and that simply C&P the contents into a new form would do the trick (and it did). I don't know why these things are happening.

The biggest problem right now is that the failsafes have been disabled. Here's an overview, if this helps:
MS Access 2003
Stored on a shared drive
Multiple users access it across multiple computers, though one at a time
Users are very limited (<5)

I really can't suspect that anyone is purposely screwing with this thing, but I can't explain these random occurances. Please help.

[janders468]

Typically this happens when, in code, someone has turned off the warnings with

docmd.setwarnings false
 

If it was never set back to true or if the program errored out or crashed before the program completed then it may never have gotten turned back on. To fix it go into a VBA window, go to the immediate window (ctrl+G) and type

docmd.setwarnings true
 

Everything should work now, but if it was turned off in code you might want to find where this happened and make sure that errors are handled, it gets turned back on, etc.

Also, this can be controlled from macros as well, so if there is macro that turns the warnings off and halted before turning them back on then this will happen as well.

Hope that helps.

[missinglinq]

DoCmd.SetWarnings is not ANYWHERE in ANY code of mine! Nonetheless, I threw it in once and set it to TRUE just to be safe. This did not remedy the problem.

janders468, you were warned earlier today about posting answers where you obviously had not bothered to carefully read the original problem. You posted back to that thread and saw that warning less than 30 minutes ago, and yet you have turned around and done the same thing again! Please stop wasting our time and bandwidth with this type of behavior. This is your final warning. Ignore it, and you will be banned from this site!

Linq

Moderator

[missinglinq]

Several questions, isoquin.

If you close the database then reopen it immediately, does the behavior persist?

What service pack/hot fixes do you have installed?

The biggest problem right now is that the failsafes have been disabled. Here's an overview, if this helps:
MS Access 2003

You say the db is stored on a shared drive. Do you mean the db is split into front end/ back end with the back end on the shared drive, or is it an unsplit db that every one is accessing from the shared drive?

You say " Multiple users access it across multiple computers, though one at a time." How can you be sure of this? I ask this because the latter option, an unsplit db on a shared drive, being shared by multiple users , is a recognized cause of repeated corruption.

Linq ;0)>