Re: The database has been placed in a state...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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



.

Relevant Pages

  • Re: Help - locked out of database
    ... IT checked all the permissions and everything seems to be ok. ... "Joan Wild" wrote: ... I have poured a year into this database - is there someway to recover this? ... You need, at minimum, modify permission on the folder. ...
    (microsoft.public.access.security)
  • Re: Probs accessing database for users of newly developed Superuse
    ... but the SuperUsers cannot get into it. ... You've double-checked their permissions and all are correct. ... I've included the code for when the form opens below. ... ' Minimize the database window and initialize the form. ...
    (microsoft.public.access.security)
  • Re: Probs accessing database for users of newly developed Superuse
    ... but the SuperUsers cannot get into it. ... double-checked their permissions and all are correct. ... I've included the code for when the form opens below. ... ' Minimize the database window and initialize the form. ...
    (microsoft.public.access.security)
  • Re: Issue: LDB Not Being Created
    ... I would totally agree that it is a rights issue (and was convinced it ... I open the database and the LDB gets created. ... file create permissions, then all other users of the network would be able ... However if one user opens up the file does not have correct permissions to ...
    (comp.databases.ms-access)
  • Re: Front end, Back end, and restrictions on which Forms can open.
    ... Joan Wild wrote: ... ensuring that 'users' were granted no permissions (as i did when i was ... using the same method and selecting the same security file. ... it is secured but when I double click on the file, it still opens ...
    (microsoft.public.access.security)