I am attempting to create a split database (see previous message) to hopefully resolve this issue, but I have not accomplished this yet.
Currently I have one database on a network folder with a primary user (Read, Read & Execute, and Write access through Properties), and a number of secondary users (Read and Read & Execute access through Properties only). The Read-Only users should be able to load the database even when the primary user is using the database, correct? The settings are Shared/No Locks/Open database using record-level locking.
The "Could not lock file" is happening even for read-only users no matter how they attempt to open the database, even if they open it with a /ro shortcut or if they open it from Access and select Open Read-Only.
Can you help me? Thanks!
Edited to add that I do not believe it's an issue with users not having Write access to the network folder where the database is stored because I have Write access to the folder (as I installed the database and various other files to that drive), and I get this issue when I attempt to open the database when another user is using it, even when I attempt to open it Read-Only.
Currently I have one database on a network folder with a primary user (Read, Read & Execute, and Write access through Properties), and a number of secondary users (Read and Read & Execute access through Properties only). The Read-Only users should be able to load the database even when the primary user is using the database, correct? The settings are Shared/No Locks/Open database using record-level locking.
The "Could not lock file" is happening even for read-only users no matter how they attempt to open the database, even if they open it with a /ro shortcut or if they open it from Access and select Open Read-Only.
Can you help me? Thanks!
Edited to add that I do not believe it's an issue with users not having Write access to the network folder where the database is stored because I have Write access to the folder (as I installed the database and various other files to that drive), and I get this issue when I attempt to open the database when another user is using it, even when I attempt to open it Read-Only.
Last edited:
