|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
The database has been placed in a state...We are using MS Office Professional 2003. We have a database that is being
accessed by a lot of people in our office. The problem is that when this particular user (user41) is the first one to open up the database in the morning nobody else can open the database unless he closes it, let's everybody open it in their computers, then he opens it again. The error that other users get on their PCs when user41 is on the database is: "The database has been placed in a state by a user "Admin" on machine "PC041" that prevents it from being opened or locked." Help! Grace You should verify that user41 (as well as all users) has
read/write/create/delete permission on the folder where the database is located. They need this in order to create the associated ldb file. Without the create permission, they can't create the ldb and therefore open the mdb exclusively. -- Show quoteHide quoteJoan Wild Microsoft Access MVP "Grace" wrote: > We are using MS Office Professional 2003. We have a database that is being > accessed by a lot of people in our office. > > The problem is that when this particular user (user41) is the first one to > open up the database in the morning nobody else can open the database unless > he closes it, let's everybody open it in their computers, then he opens it > again. > > The error that other users get on their PCs when user41 is on the database is: > > "The database has been placed in a state by a user "Admin" on machine > "PC041" that prevents it from being opened or locked." > > Help! > > Grace Hi Joan,
Thank you for replying. The groups that the users belong to have modify permissions. Could not having delete permissions have something to do with it? Also, from what I understand, the ldb file is created when the database is opened and gets deleted when the program is closed. I opened the ldb file with notepad while the database is opened by someone else and this is how it looked like. PC032 Admin PC041 Admin Is there something wrong with this file? -- Show quoteHide quoteGrace "Joan Wild" wrote: > You should verify that user41 (as well as all users) has > read/write/create/delete permission on the folder where the database is > located. They need this in order to create the associated ldb file. Without > the create permission, they can't create the ldb and therefore open the mdb > exclusively. > > -- > Joan Wild > Microsoft Access MVP > > > "Grace" wrote: > > > We are using MS Office Professional 2003. We have a database that is being > > accessed by a lot of people in our office. > > > > The problem is that when this particular user (user41) is the first one to > > open up the database in the morning nobody else can open the database unless > > he closes it, let's everybody open it in their computers, then he opens it > > again. > > > > The error that other users get on their PCs when user41 is on the database is: > > > > "The database has been placed in a state by a user "Admin" on machine > > "PC041" that prevents it from being opened or locked." > > > > Help! > > > > Grace I was referring to Windows permissions. *All* users need create and delete
permissions on the folder. Once everyone is out, check that the ldb disappears. If it's still there, delete it. -- Show quoteHide quoteJoan Wild Microsoft Access MVP Grace wrote: > Hi Joan, > > Thank you for replying. The groups that the users belong to have > modify permissions. Could not having delete permissions have > something to do with it? Also, from what I understand, the ldb file > is created when the database is opened and gets deleted when the > program is closed. I opened the ldb file with notepad while the > database is opened by someone else and this is how it looked like. > > PC032 Admin PC041 > Admin > > Is there something wrong with this file? > -- > Grace > > "Joan Wild" wrote: > >> You should verify that user41 (as well as all users) has >> read/write/create/delete permission on the folder where the database >> is located. They need this in order to create the associated ldb >> file. Without the create permission, they can't create the ldb and >> therefore open the mdb exclusively. >> >> -- >> Joan Wild >> Microsoft Access MVP >> >> >> "Grace" wrote: >> >>> We are using MS Office Professional 2003. We have a database that >>> is being accessed by a lot of people in our office. >>> >>> The problem is that when this particular user (user41) is the first >>> one to open up the database in the morning nobody else can open the >>> database unless he closes it, let's everybody open it in their >>> computers, then he opens it again. >>> >>> The error that other users get on their PCs when user41 is on the >>> database is: >>> >>> "The database has been placed in a state by a user "Admin" on >>> machine "PC041" that prevents it from being opened or locked." >>> >>> Help! >>> >>> Grace Hi Joan,
Yes, I was referring to Windows permissions also. In the permissions for the folder, under advanced Modify includes Delete but not Delete Subfolders and Files -- Show quoteHide quoteGrace "Joan Wild" wrote: > I was referring to Windows permissions. *All* users need create and delete > permissions on the folder. > > Once everyone is out, check that the ldb disappears. If it's still there, > delete it. > > > -- > Joan Wild > Microsoft Access MVP > > Grace wrote: > > Hi Joan, > > > > Thank you for replying. The groups that the users belong to have > > modify permissions. Could not having delete permissions have > > something to do with it? Also, from what I understand, the ldb file > > is created when the database is opened and gets deleted when the > > program is closed. I opened the ldb file with notepad while the > > database is opened by someone else and this is how it looked like. > > > > PC032 Admin PC041 > > Admin > > > > Is there something wrong with this file? > > -- > > Grace > > > > "Joan Wild" wrote: > > > >> You should verify that user41 (as well as all users) has > >> read/write/create/delete permission on the folder where the database > >> is located. They need this in order to create the associated ldb > >> file. Without the create permission, they can't create the ldb and > >> therefore open the mdb exclusively. > >> > >> -- > >> Joan Wild > >> Microsoft Access MVP > >> > >> > >> "Grace" wrote: > >> > >>> We are using MS Office Professional 2003. We have a database that > >>> is being accessed by a lot of people in our office. > >>> > >>> The problem is that when this particular user (user41) is the first > >>> one to open up the database in the morning nobody else can open the > >>> database unless he closes it, let's everybody open it in their > >>> computers, then he opens it again. > >>> > >>> The error that other users get on their PCs when user41 is on the > >>> database is: > >>> > >>> "The database has been placed in a state by a user "Admin" on > >>> machine "PC041" that prevents it from being opened or locked." > >>> > >>> Help! > >>> > >>> Grace > > > I would still double-check the windows permissions for the problem user.
They are somehow opening the file exclusively. If the permissions are correct, check to see if they are using a shortcut with the /excl switch or using File, Open Exclusive. I'm betting permissions. -- Show quoteHide quoteJoan Wild Microsoft Access MVP Grace wrote: > Hi Joan, > > Yes, I was referring to Windows permissions also. In the permissions > for the folder, under advanced Modify includes Delete but not Delete > Subfolders and Files > -- > Grace > > > "Joan Wild" wrote: > >> I was referring to Windows permissions. *All* users need create and >> delete permissions on the folder. >> >> Once everyone is out, check that the ldb disappears. If it's still >> there, delete it. >> >> >> -- >> Joan Wild >> Microsoft Access MVP >> >> Grace wrote: >>> Hi Joan, >>> >>> Thank you for replying. The groups that the users belong to have >>> modify permissions. Could not having delete permissions have >>> something to do with it? Also, from what I understand, the ldb file >>> is created when the database is opened and gets deleted when the >>> program is closed. I opened the ldb file with notepad while the >>> database is opened by someone else and this is how it looked like. >>> >>> PC032 Admin PC041 >>> Admin >>> >>> Is there something wrong with this file? >>> -- >>> Grace >>> >>> "Joan Wild" wrote: >>> >>>> You should verify that user41 (as well as all users) has >>>> read/write/create/delete permission on the folder where the >>>> database is located. They need this in order to create the >>>> associated ldb file. Without the create permission, they can't >>>> create the ldb and therefore open the mdb exclusively. >>>> >>>> -- >>>> Joan Wild >>>> Microsoft Access MVP >>>> >>>> >>>> "Grace" wrote: >>>> >>>>> We are using MS Office Professional 2003. We have a database that >>>>> is being accessed by a lot of people in our office. >>>>> >>>>> The problem is that when this particular user (user41) is the >>>>> first one to open up the database in the morning nobody else can >>>>> open the database unless he closes it, let's everybody open it in >>>>> their computers, then he opens it again. >>>>> >>>>> The error that other users get on their PCs when user41 is on the >>>>> database is: >>>>> >>>>> "The database has been placed in a state by a user "Admin" on >>>>> machine "PC041" that prevents it from being opened or locked." >>>>> >>>>> Help! >>>>> >>>>> Grace
Secured Database works exactly right on one computer, but on another not quite r
More security questions Getting started with security Frontend Downloads Access 2003 on wondows XP de-secure problem Is it any way to programmatically store and hide data inside an Access database that it is not shown Mystery security group setting changes. add tick boxes inside table Read only report Locked out of Access |
|||||||||||||||||||||||