Results 1 to 11 of 11
  1. #1
    2 Star Lounger
    Join Date
    Jun 2001
    Location
    Virginia, USA
    Posts
    127
    Thanks
    0
    Thanked 0 Times in 0 Posts

    file already in use. (Error 3045) (Access XP)

    The following error message keeps appearing when multiple users of a split db attempt to use the same back-end db. This is an unsecured database (no users, groups, passwords...). Back-end about 58.5MB, front-end about 11.7 (MDE). The front-end and back-end "Tools | Options | Advanced | Default Open Mode" is set to Shared.

    Could not use <name>; file already in use. (Error 3045)
    The specified file is currently being used by another user or session. Wait for the other user or session to finish working with the file, and then try the operation again.

    Just to be sure the tables were linked properly, I went to the Linked Table Manager to refresh links (would like to find a way to have this done automatically when users open their front end. I'll search the forums for this one.) and was told that the first table in the list was "already in use..."

    Are there some properties that I may have overlooked to prevent multiple users for simultaneously using the same back-end? Also, is there some limit to the number of front-end users that can hit the same back-end simultaneously? Any suggestions or reference material is welcome.

    Many thanks,

  2. #2
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: file already in use. (Error 3045) (Access XP)

    Check to see if one or more users have the option when the open the database to exclusive. If that's not it, is someone opening an object in design mode - that will set the system to exclusive use. As to the limit, the system specification is 255 users from memory, though I certainly wouldn't try that with an Access based back-end.
    Wendell

  3. #3
    2 Star Lounger
    Join Date
    Jun 2001
    Location
    Virginia, USA
    Posts
    127
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: file already in use. (Error 3045) (Access XP)

    Thanks Wendell,

    It turns out that one of the users was in the back-end in design mode, "...just checking it out...". (despite my request to all users not to open the back-end) Is there a way, on our network to hide the back end database? I think it is easy enough for some users to know how to "show hidden objects". Is there a way for me to assign some form of security that prohibits users from seeing the back end databases without hindering their ability to use the front end? I am currently reviewing "Manage user and group accounts" from help. Any other resources appreciated.

    Many thanks,

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: file already in use. (Error 3045) (Access XP)

    If you want to know more about user-level security, this is very useful: ACC2000: Microsoft Access Security FAQ Available in Download Center.

  5. #5
    2 Star Lounger
    Join Date
    Jun 2001
    Location
    Virginia, USA
    Posts
    127
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: file already in use. (Error 3045) (Access XP)

    Thanks.
    In my quest to secure the back end databases, I think I locked myself out. I am trying to understand how to give myself the privliges needed to look at the back-end tables. (see error message below.)

    ...You do not have the necessary permissions to use the <name> object. Have your system administrator or the person who created this object establish the appropriate permissions for you. (Error 3033)

    I was trying to reset the settings back the way they were before I made changes. I opened the back-end database, and did the following:
    Tools | Security | User Groups and Permissions |
    User/Group name: Admin Object Name: <Current Database>

    and selected Object Type "Database" then unchecked "Open Exclusive"

    What should the setting be so that I can view the contents of the back-end tables?

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: file already in use. (Error 3045) (Access XP)

    I suspect Hans has probably turned in for the night (he's in Europe), so I'll take a shot at your situation. Removing the Open Exclusive permission should not have caused you any problem. More probably you have blocked the Admin account from seeing the tables by changing some permssions. Unless you have create another secure administrative account, you want Admin to have full priviledges on everything. It also sounds as if you may need to take a look at the Microsoft article that Hans suggested. At this stage Admin is probably still the owner of the back end mdb, so you should be able to set your priviledges.
    Wendell

  7. #7
    2 Star Lounger
    Join Date
    Jun 2001
    Location
    Virginia, USA
    Posts
    127
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: file already in use. (Error 3045) (Access XP)

    Wendell, Hans, et.al.,
    First, I am reading the document Hans suggested and it appears that one way to solve my problem is to create a new blank database and import the tables into it. Apparently, permissions are not imported with objects. I will try this tomorrow. (It is now late here too.) But, I have a couple of questions if you please.

    1. The "Open Exclusive" means that the user may perform any action that requires the database, table, or other object to be opened exclusively. It does not mean that when the user uses the database, it is always exclusively. Is this correct?

    2. How can I tell if I am Admin when I log in, and what permissions I have?

    3. I noticed that the "Open/Run" is disabled. Has Admin been altered some way to disable this?

    4. When I attempt to open the Back-end database on the server, I get the following message...

    Could not lock file. (Error 3050)
    The operating system will not allow Microsoft

  8. #8
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: file already in use. (Error 3045) (Access XP)

    The "Could not lock file. (Error 3050)" error seems to indicate that you don't have sufficient rights in the network folder where the backend database is stored. Access requires that every user of a database has change rights (read/write/create/delete) in this folder.

  9. #9
    3 Star Lounger
    Join Date
    Jan 2001
    Location
    Edmonton, Alberta, Canada
    Posts
    326
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: file already in use. (Error 3045) (Access XP)

    This might sound like a stupid question, but just to cover all possibilities - the users do have write access to the directory that the backend is in (i.e. so that files can be created and deleted), correct? Problems with creating/deleting the lock file can cause multi-user problems.

  10. #10
    2 Star Lounger
    Join Date
    Jun 2001
    Location
    Virginia, USA
    Posts
    127
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: file already in use. (Error 3045) (Access XP)

    Well all,
    The network guys changed the permissions on the network folder where the back-end of this distributed database lives. Now everyone who needs to get to it can, including me. I am reviewing the rules on securing a database now but am curious about one thing regarding split databases. If I password protect the back-end, can I encode that password in the users' front-ends so they can function normally without having to know the back-end password? (see where I'm going with this?)

    Thanks again for all your help and suggestions.

  11. #11
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: file already in use. (Error 3045) (Access XP)

    If you really want to protect your database, user-level security is the way to go. A database-level password is not really secure - you can buy password-crackers.

Posting Permissions

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