Preventing locking

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Gallows
    New Member
    • Aug 2007
    • 1

    Preventing locking

    Hi

    This is my first post so I hope I can make my problem understandable (?)

    I have an Access database which is used by approx 8-10 users at a time. On a intermittant basis, users are getting a message "Could not update; currently locked by user 'Admin' on machine '[machine no]'". The 'offending machine is always the same one. This user is not opening the database exclusively or in any other obvious way to cause the problem. I have looked at the Access settings and cannot see any obvious reason for this to occur. Our organisation uses a modified version of Windows XP.

    Any ideas of what may be the problem and suggestions to fix it would be gratefully received.

    Thanks

    David
  • dima69
    Recognized Expert New Member
    • Sep 2006
    • 181

    #2
    Originally posted by Gallows
    Hi

    This is my first post so I hope I can make my problem understandable (?)

    I have an Access database which is used by approx 8-10 users at a time. On a intermittant basis, users are getting a message "Could not update; currently locked by user 'Admin' on machine '[machine no]'". The 'offending machine is always the same one. This user is not opening the database exclusively or in any other obvious way to cause the problem. I have looked at the Access settings and cannot see any obvious reason for this to occur. Our organisation uses a modified version of Windows XP.

    Any ideas of what may be the problem and suggestions to fix it would be gratefully received.

    Thanks

    David
    Looks like your question is quite a complicated one. Maybe some more details will help, like:
    Are you using Front End - Back End DB configuration ?
    What access version are you running ?
    What network protocol is there ?
    What kind of record locking is there ?
    What is different about the 'offending' machine ?
    Does it happen even if the database is not opened on that machine ?

    Comment

    • Briansmi1116
      New Member
      • Oct 2007
      • 76

      #3
      I have the similar problem, I am running Acces 2003 and Windows XP. This problem is causeing the Database not to be used. My egineer opens it in the morning, and leaves it open all day. Most of the time he is just viewing it, but he does edit the records, and adds new ones. Every now and then, nobody else can enter into the database, because it is locked out by him. any ideas?

      Brian

      Comment

      • Curben
        New Member
        • Oct 2007
        • 47

        #4
        Originally posted by Briansmi1116
        I have the similar problem, I am running Acces 2003 and Windows XP. This problem is causeing the Database not to be used. My egineer opens it in the morning, and leaves it open all day. Most of the time he is just viewing it, but he does edit the records, and adds new ones. Every now and then, nobody else can enter into the database, because it is locked out by him. any ideas?

        Brian
        Brian, in your case I get the feeling you do not have a secure database. If you create a secure database then you should be able to have multiple users access the database. My question is this, Does the engineeer need it open all day, or is he forgetting about it. I have worked with some forgetful users who open a DB and leave it open so we scheduled a program close.

        Comment

        • Briansmi1116
          New Member
          • Oct 2007
          • 76

          #5
          He seems to want it open all day, although he might forget about it. I don't think he would mind if it closed after an amount of time, where he is not using it.

          Comment

          • Curben
            New Member
            • Oct 2007
            • 47

            #6
            Originally posted by Briansmi1116
            He seems to want it open all day, although he might forget about it. I don't think he would mind if it closed after an amount of time, where he is not using it.
            If he needs it open all day the addings security may be your best bet. by being logged in as seperate users multiple people should be able to access

            Comment

            • Briansmi1116
              New Member
              • Oct 2007
              • 76

              #7
              Can you tell me exactlly how I would do this?

              Comment

              • Curben
                New Member
                • Oct 2007
                • 47

                #8
                Originally posted by Briansmi1116
                Can you tell me exactlly how I would do this?


                There should be an access security wizard to walk you through most of the steps. In 2003 It's in : Tools > Security

                Comment

                • Briansmi1116
                  New Member
                  • Oct 2007
                  • 76

                  #9
                  I went through the wizard, and it just does the security to my computer. Now I have to enter a password, whenever I open a database. This is with all of the databases I have access to. How can I remove this, and be able to do what I want?

                  Comment

                  • Briansmi1116
                    New Member
                    • Oct 2007
                    • 76

                    #10
                    Never mind I got rid of it. But I still will have the locking problem.

                    Comment

                    • Curben
                      New Member
                      • Oct 2007
                      • 47

                      #11
                      Originally posted by Briansmi1116
                      Never mind I got rid of it. But I still will have the locking problem.
                      Did you have the locking problem while security was enabled?

                      Yes security will require the use of Usernames and Passwords, but as far as I know it is the only way to allow multiple people to access the DB Simultaneously.

                      Once it is enabled, it is possible to create a shortcut that will open the Database and login for you. In that same shortcut you can also link to the workgroup file used so you will not have to change the default

                      Use this as an Example Shortcut Target
                      Code:
                      "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" 
                      "\\127.0.0.1\Project\Project.mdb" 
                      /wrkgrp "\\127.0.0.1\Project\ProjectFiles\Security\Project.mdw"
                      /User "MyName" 
                      /Pwd "MyPa55word"
                      Link to the Access Program
                      Then the file
                      Then the workgroup
                      Followed by username and password

                      Comment

                      Working...