If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Access database placed in a state...
I have a multi-user Acess database that has somehow become attached to one
specific user. For some reason, whenever this user opens the Database, it locks everyone else out. This user has apparently become "admin" Error message - The database has been placed in a state by user name on machinename that prevents it from being opened or locked. (Error 3734) How can I turn off this passive shutdown/connection control |
#2
|
|||
|
|||
Access database placed in a state...
First off, if your database is multi-user it needs to be split. You need a
front end and back end. You may already have that set up, but if not you need to. Secondly, the backend file AND the folder it resides in must have read/write/edit/ and delete rights for each user. "SimpleUser" wrote: I have a multi-user Acess database that has somehow become attached to one specific user. For some reason, whenever this user opens the Database, it locks everyone else out. This user has apparently become "admin" Error message - The database has been placed in a state by user name on machinename that prevents it from being opened or locked. (Error 3734) How can I turn off this passive shutdown/connection control |
#3
|
|||
|
|||
Access database placed in a state...
=?Utf-8?B?R29sZmlucmF5?= wrote
in news Secondly, the backend file AND the folder it resides in must have read/write/edit/ and delete rights for each user. Technically, the back end folder does not require delete rights -- it will run just fine without it, though the LDB file will never be deleted. The usual reason for doing this is to prevent users from accidentally deleting your back-end data file. The minor downside is that the LDB file won't be deleted when the last user exits your app. This is only a problem if the LDB file gets corrupted, and in that case, someone with delete permissions can take care of it. My usual practice when I removed delete permissions was to have regulars users without delete permissions and a few administrative users *with* delete permissions (the couple of people who did database maintenance). This has worked fine for years in several installations I've had. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ |
Thread Tools | |
Display Modes | |
|
|