Not confirming anything

Topic

New Reply

This is not a big deal, but it is bugging me.

I’ve got this database that I only use once a year to import records into another database (which is why this isn’t a big deal). I noticed that when I delete a table or run an update query, I didn’t get any system message telling me what I am about to do and making sure I want to do it. I checked the settings under Tools|Options, and in the “Edit” tab all 3 entries in the “Confirm” box are checked (“Record Changes”, “Document Deletions”, “Action Queries”).

So is there another setting I’m missing that overrules those “Confirm” settings? Like I said, it isn’t a big deal; I just feel kind of stupid not knowing why it is acting this way.

Reply | Quote

Replies

Mark

Are these actions happening manually ? or via code?
The only thing I can think of that overrides these settings is

Code:

Docmd.SetWarnings False

commonly put in code for just this purpose.

Reply | Quote

Mark

Are these actions happening manually ? or via code?
The only thing I can think of that overrides these settings is

Code:

Docmd.SetWarnings False

commonly put in code for just this purpose.

No code exists to set warnings = false. I’m running everything from db window.

Reply | Quote

Following on to John’s comment, is it possible that some code was run to set the warnings to false, and either there was nothing to set it back to true, or the code crashed at some point. I have seen that behavior – but setting the warnings to true in the immediate window fixed things.

Reply | Quote

Following on to John’s comment, is it possible that some code was run to set the warnings to false, and either there was nothing to set it back to true, or the code crashed at some point. I have seen that behavior – but setting the warnings to true in the immediate window fixed things.

No chance warnings were set to False via code. There are only about 10 lines of code in entire db!

As I said, this is not really a big issue in this circumstance. Whether or not I actually “fix” it for this db is inconsequential. To me, the more important issue is what setting is causing this behavior?

Reply | Quote

I found similar behaviour after I had used an add-in (IIRC it was Helen Feddema’s rename add-in).

Closing and re-opening Access cured it so I guess it was a DoCmd SetWarnings False not followed by a reset to True.

Reply | Quote

I found similar behaviour after I had used an add-in (IIRC it was Helen Feddema’s rename add-in).

Closing and re-opening Access cured it so I guess it was a DoCmd SetWarnings False not followed by a reset to True.

I didn’t use an add-in. I didn’t SetWarnings to False.

Reply | Quote