Access Database - Locked out from Design

[Guest]

I have a database where the front end and back end are both on a network
server. I will eventually put the front end on each users desktop. Right
now I am having problems with the database locking up. I can copy my revised
front end mdb to the old mdb even though it shows it is locked for design.
But I am worried that this may cause corruption. Additionally, if I need to
add a field to a table in the back end database, I cannot because it is
locked along with the front end.

There are only three users of this database and they all log out with no
problem. However, it shows that someone is still in it - usually it is the
first person who logged into the database. The network administrator usually
has to reboot the server in order to unlock that database. Is anyone out
there familiar with this happening? Is this a server issue? What can be
done to stop the database from hanging up like this?

 

[J_Goddard via AccessMonster.com]

Hi -

Yes, it might be a server issue, but not a server problem.

When you say "...it shows that someone is still in it...", how are you
determining that? If you are determining that by seeing an .ldb file when no
one is in the database, it probably means that your users do not have delete
permission in the directory where the database resides. Check with your lan
administrator to ensure that they are given delete permission.

I would suggest, too, that you have the front end and back end in different
directories.

HTH

John

 

[Guest]

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.

 

[J_Goddard via AccessMonster.com]

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

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]

 

[Pete D.]

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.

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

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?

 

[Guest]

Thanks for the responses and suggestions!

It varies as to who is holding the ldb file open --- I think it is whoever
accesses the database first (there are only 3 users). This morning the
database was locked, showing User A as the owner. I asked User A to try to
delete the lbd file, but she couldn't. She said she received an error saying
that the file was being used by another user and she could not delete it.
Even though the security properties of the lbd file show that she is the
"owner."

Regarding the possibility of a network/pc problem, two of the users are
locally connected to the server. I, on the other hand, access the database
remotely using remote desktop connection via a VPN. Since they are local,
could they still have a connection problem? Could the connection problem be
me? When I log in at night with no one else logged in and the database is
not locked. I can go in and out and never lock myself out.

Any advice is much appreciated!

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.

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

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?

 

[Pete D.]

I think you may have answered you own question, skip a few days. Pete D.

Thanks for the responses and suggestions!

It varies as to who is holding the ldb file open --- I think it is whoever
accesses the database first (there are only 3 users). This morning the
database was locked, showing User A as the owner. I asked User A to try
to
delete the lbd file, but she couldn't. She said she received an error
saying
that the file was being used by another user and she could not delete it.
Even though the security properties of the lbd file show that she is the
"owner."

Regarding the possibility of a network/pc problem, two of the users are
locally connected to the server. I, on the other hand, access the
database
remotely using remote desktop connection via a VPN. Since they are local,
could they still have a connection problem? Could the connection problem
be
me? When I log in at night with no one else logged in and the database is
not locked. I can go in and out and never lock myself out.

Any advice is much appreciated!

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.

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?