Re: Access Database - Locked out from Design

Check everything mentioned first and then check and see who is holding the
ldb file open. bad network connection could also cause this so once you
identify user you can solve the pc/network problem.
"J_Goddard via AccessMonster.com" <u37558@uwe> wrote in message
news:79666d17ab82a@xxxxxx
Hi -

What happens if the 'owner' of the ldb file tries to delete it? If they
are
able to delete it (with no one in the database), it again points to a
permissions issue - maybe your permissions are set up such that only the
owner of a file can delete it, which would explain why you can't.

Consider this scenario, where there is no .ldb file:

1- User "A" opens the database, and Access creates the .ldb file in the
process
2- User "B" also opens the database
3- User "A" exits the database, but Access cannot delete the .ldb file
because User "B" is still in the database
4- User "B" exits the database, but Access still cannot delete the .ldb
file,
because it is 'owned' by User "A".

Now you have your situation, an .ldb file existing with no one in the
database.

Check with your LAN people on this.

Sorry about using the word 'directories' for file location - it's oldspeak
for folders. I did mean that front end and back end be in separate
folders.

John


Tammy wrote:
Thanks for responding, John. I know that no one is in the database,
because
they all confirm to me they are out. But I cannot make any changes to the
design because it's as if someone is still in. I can see the locking file
(lbd?) -- and when I go into the properties of that file and view the
owner,
it is usually the first person who opened the database. I have tried to
delete that locking file, but it won't allow me to. I have also tried to
change the ownership to me, to no avail.

All users have full access/permissions to that directory and drive and
have
the delete permission. What will happen if I copy the mdb file while it
is
locked, make changes and then copy it back? Will I be exposing the
database
to corruption?

The front end and back end are located in two different subfolders, but
you
say they should be in different directories? Will that help with the
locking? Should the directory where the back end resides, have any
special
permission set up? Should all users have delete permissions?

Sorry for all the questions. Right now, every time I need access to edit
the
design or copy the revised database over, we have to reboot the server.
Also, since I do not have access to reboot, I have to wait for someone
else
to do this -- and many times they forget and I am stuck without the
ability
to make changes.

Thank you so much for your help.

Hi -

[quoted text clipped - 28 lines]
there familiar with this happening? Is this a server issue? What can
be
done to stop the database from hanging up like this?

--
Message posted via http://www.accessmonster.com



.

Relevant Pages

  • RE: Check for Exclusive
    ... revise and implement it into our live database. ... "Paolo" wrote: ... Look at the size of the ldb file. ... If a user opens the database when it was not previously open, ...
    (microsoft.public.access.modulesdaovba)
  • Re: .ldb files
    ... Unless the users have full rights to the folder that the database ... meaning that if a .ldb file exists (Someone has ... so opens the file as read only). ...
    (microsoft.public.access.security)
  • Re: .ldb files
    ... >> that Microsoft could and should rectify! ... >> created a database which merges data from two folders. ... so opens the file as read only). ... >> Surely if when Access fails to create a .ldb file it ...
    (microsoft.public.access.security)
  • Re: close / rename linked .mdb file
    ... except when Access "opens" it to deal with the ... code in the startup procedure which opens a database or recordset ... Opening the .ldb file using notepad will show you both who's currently ... Determining the workstation which caused the Microsoft Access MDB ...
    (microsoft.public.access.modulesdaovba)
  • RE: The database has been placed in a state...
    ... Could not having delete permissions have something to do with ... Also, from what I understand, the ldb file is created when the database ... he closes it, let's everybody open it in their computers, then he opens it ...
    (microsoft.public.access.security)
Loading