Results 1 to 7 of 7
  1. #1
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts
    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.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  2. #2
    Super Moderator
    Join Date
    Jun 2002
    Location
    Mt Macedon, Victoria, Australia
    Posts
    3,993
    Thanks
    1
    Thanked 45 Times in 44 Posts
    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.
    Regards
    John



  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts
    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.
    Wendell

  4. #4
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts
    Quote Originally Posted by John Hutchison View Post
    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.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  5. #5
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts
    Quote Originally Posted by WendellB View Post
    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?
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  6. #6
    4 Star Lounger SteveH's Avatar
    Join Date
    Jan 2001
    Location
    Chelsea, Gtr London, United Kingdom
    Posts
    587
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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.
    Steve H
    IT Lecturer/Access Developer
    O2K SR3/O2010; Win7Pro

  7. #7
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts
    Quote Originally Posted by SteveH View Post
    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.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •