Access keeps autosaving

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MattGaff
    New Member
    • Oct 2007
    • 24

    Access keeps autosaving

    I am sure I have done something but cannot work out how to undo....

    Everytime I go to a new query and create something, when I close it down, it doesn't give me the option of "Do you want to save the query" (or something like this.
    Instead, it acts as if I automatically want to save it which is starting to really annoy me now.
    Did a quick google search but could not find anything. Does anybody have any ideas how to return my database to normal?
  • missinglinq
    Recognized Expert Specialist
    • Nov 2006
    • 3533

    #2
    Is it actually saving the query? How can it save a new query, without at least asking for a name? Is the query actually saved? If so, how do you know? What name is it saved under?

    Linq ;0)>

    Comment

    • MattGaff
      New Member
      • Oct 2007
      • 24

      #3
      Sorry yeah, the pop up for a name shows.
      But usually, before this pop up it at least asks you if you want to save it. When you click YES, the "What do you want to save as" box appears -i.e. what I am getting.

      Comment

      • DonRayner
        Recognized Expert Contributor
        • Sep 2008
        • 489

        #4
        My guess is that you have the the warnings turned off. Try entering the following in the immediate window of your visual basic editor. If it works you will have to track down where you are actually setting the warnings off.

        Code:
        docmd.SetWarnings true

        Comment

        • MattGaff
          New Member
          • Oct 2007
          • 24

          #5
          Originally posted by DonRayner
          My guess is that you have the the warnings turned off. Try entering the following in the immediate window of your visual basic editor. If it works you will have to track down where you are actually setting the warnings off.

          Code:
          docmd.SetWarnings true

          Yep, that's done it. I knew exactly where I had that as well. I imported some code from somewhere where that had set. Cheers

          Comment

          • missinglinq
            Recognized Expert Specialist
            • Nov 2006
            • 3533

            #6
            Code with

            DoCmd.SetWarnin gs False

            always, always, always needs

            DoCmd.SetWarnin gs True

            It's one of those things Access should do automatically, like an End Sub when you start a writing a sub!

            Linq ;0)>

            Comment

            Working...