none
The database has been placed in a state by user 'Admin' on machine RRS feed

  • Question

  • Greetings,

    I created a database on a shared network folder, which everyone has read/write access.  I manually split the database by:

    1. Making a copy of the original

    2. Deleting all the queries/forms/reports/modules inside the Copy, leaving just the table, thus creating the back end (BE).  I also put a password protect on the BE

    3. Deleting the tables in the original, and re-linking the tables to the BE, thus creating the front end (FE)

    4. I distributed the FE to multiple users

    Multiple users can open the FE database, but when a user opens a form to add/edit existing data in a table, it prevents other users from opening the FE database and gives the "The database has been placed in a state by user 'Admin' on machine...". 

    I verified that the form properties has Record Locks to "No Locks".  Can anyone please help troubleshoot why this is happening??  Thank you in advance for your help!

    EDIT 8/30/17 with resolution steps:

    Just wanted to give an update with what happened in case it is
    able to help others who may be running into the same issue:

    1.  Started from square 1 before 'splitting' the database by taking my most
    recent backup and made a copy of the backup

    2.  I then deleted all of the queries/forms/reports/modules/macros from the
    Copy, leaving only the tables

    3.  I used Access' Splitter to split the database, putting the BE on the
    network drive

    4.  I then imported all of queries/forms/reports/modules/macros into the
    FE

    I have no idea why this now allows multiple users to add/edit using the FE
    without locking the BE.  I don't know how this was any different than when I
    manually split the database other than using Access' splitter tool.  Thank you
    to everyone to responded.  I will definitely adjust the database to bind the
    forms to queries instead of tables as recommended.

    • Edited by JT564 Wednesday, August 30, 2017 8:04 PM
    Tuesday, August 29, 2017 4:35 PM

All replies

  • Hi,

    Do all users with FEs have full permission to the folder where the BE is located? Make sure they have read/write/modify/delete permissions to the BE folder.

    Hope it helps...

    Tuesday, August 29, 2017 5:16 PM
  • The first thing I would do is identify the user who is locking the database and check to see if he/she is accidentally opening the database for exclusive use by default. This can also happen if a user opens an object in design mode.

    Paul ~~~~ Microsoft MVP (Visual Basic)

    Tuesday, August 29, 2017 5:22 PM
  • Hi .theDBguy - Yes, we've verified that everyone has read/write access to the location of the BE folder. Still getting the error :(
    Tuesday, August 29, 2017 6:27 PM
  • Hi Paul - It's not one user in particular.  It's just whoever has the FE open at the time.  For example, I copy/pasted the FE onto my desktop and opened the FE.  This is now preventing other users from opening forms/reports in their FE files. 

    I do not believe my FE is opening the BE in exclusive use by default.  Is there any way to verify?


    Whenever someone opens their FE file, the BE on the network creates a .laccdb file and prevents others from opening the BE for changes.  Is there anything I can do to prevent this from locking others out of the BE?
    • Edited by JT564 Tuesday, August 29, 2017 6:34 PM
    Tuesday, August 29, 2017 6:30 PM
  • Hi .theDBguy - Yes, we've verified that everyone has read/write access to the location of the BE folder. Still getting the error :(

    Okay. Do you know if the install of Access on everyone's machine is set to a particular locking default (e.g. pessimistic)?

    Tuesday, August 29, 2017 6:44 PM
  • I've verified those same settings on my computer.  I then opened my FE file and asked a co-worker to open their FE file.  My co-worker still receives the "The database has been placed in a state by user ..." error message
    Tuesday, August 29, 2017 6:46 PM
  • Hi,

    Just to isolate your application, could you create a brand new database with one table and one form bound to the table, split them up, put the BE in the same folder as the original BE and then have a co-worker open the test FE at the same time as you?

    Just trying to troubleshoot if it's your app or Access or something else...

    Tuesday, August 29, 2017 6:52 PM
  • Hi .theDBguy - Yes, we've verified that everyone has read/write access to the location of the BE folder. Still getting the error :(
    Users need delete permissions as well as read/write on the BE folder. It might be the locking file is hanging. That would prevent others from connecting.

    Bill Mosca
    www.thatlldoit.com
    http://tech.groups.yahoo.com/group/MS_Access_Professionals

    Tuesday, August 29, 2017 7:10 PM
  • Users need delete permissions as well as read/write on the BE folder. It might be the locking file is hanging. That would prevent others from connecting.


    This is a good point. Earlier, I said to check for Read, Write, Modify, and Delete, so I hope you checked all four. There's one more that might matter: Execute permission. Just to be safe, just make sure all users have "full" permission to the shared folder. You can then trim down the permission once you get the setup to work.

    Cheers!

    Tuesday, August 29, 2017 7:16 PM
  • I have seen this before.  We resolved by running Windows & Office Update on the PC locking the application.  Also some PCs required "Disk Cleanup" and "Clean up system files" before a successful update could take place.



    If this post answered or helped you find the answer to your question, please mark it as such for other Forum users knowledge.

    Tuesday, August 29, 2017 7:21 PM
  • I did this exact test and can confirm that the 'simple' database did not have any issues.  My co-worker and I were able to edit/add information to the tables at the same time without the error
    Tuesday, August 29, 2017 7:25 PM
  • I can verify users have read, write, modify, and delete rights to the network folder.  I ran a test by creating a 'simple' database with 1 table, split the 'simple' database, and was able to add/edit data on 2 different accounts at the same time.  I do not think it is a network accessibility issue.
    Tuesday, August 29, 2017 7:29 PM
  • I can verify users have read, write, modify, and delete rights to the network folder.  I ran a test by creating a 'simple' database with 1 table, split the 'simple' database, and was able to add/edit data on 2 different accounts at the same time.  I do not think it is a network accessibility issue.

    This tells me, right or wrong, the problem must be within your application. For example, are you using any code to modify the data in the tables behind your forms? If so, you may be inadvertently creating a conflict when a user edits the data on a form while at the same time some code is firing to make table changes as well.

    Just a thought...

    Tuesday, August 29, 2017 7:33 PM
  • Is it possible for me to upload my database (after stripping it of the information inside the tables)? I do have macros but they are not making changes to tables...that I can see
    Tuesday, August 29, 2017 8:01 PM
  • Is it possible for me to upload my database (after stripping it of the information inside the tables)? I do have macros but they are not making changes to tables...that I can see

    Hi,

    Unfortunately, this forum does not allow file attachments. You can share your file through a file-sharing site, like OneDrive and post a link; however, it might mean we can see your file but not able to send it back (unless the person also shares it using a file-sharing site).

    Another option is to post your question at UtterAccess (with a link to this thread to address cross-posting) because they allow file attachments there.

    Just my 2 cents...

    Tuesday, August 29, 2017 8:06 PM
  • One quick test would be to disable your macros and see if the lock error disappears.

    Just my 2 cents...

    Tuesday, August 29, 2017 8:08 PM
  • Hello,

    I notice you edit the original post and share the solution. I suggest you post the solution again and mark it as answer to close this thread.

    I followed your steps to manually split the database but failed to reproduce the issue.Since the issue exists for specific database, you may share it here so that we could troubleshoot the issue. You could also delete the Access objects one by one to narrow down the issue.

    Regards,

    Celeste


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, September 5, 2017 8:38 AM
    Moderator