Per Nick Coe (UK):
Quote:
Or you've got an unbalanced DoCmd.SetWarnings False
somewhere in your code. That turns those warnings off.
DoCmd.Setwarnings True turns them on. |
Rebooted Windows, went back in, and the problem had gone away.
Then, after jumping to cause, I read your post. Checked my code, found not one
but *two* situations where I'd neglected to set warnings back on.
Usually when I type .SetWarnings False, I automatically go down a line and type
..SetWarnings True.....Just like balancing out With...End With and
If...Else...End If.... I guess I'm slipping...
--
PeteCresswell