ldb file is visible after databases are close

[John]

Hi All,

I have encountered a problem with the ldb file of a database. When
making changes to the backend databases I need exclusive access to make
changes. I usually do this at night when all users have left the premises,
but for the last couple of nights there are no users using the database
and the ldb file is still visible even though I'm sure nobody is using
the database. I have tried to manually delete the lbd file but the
following day users encountered problems with database so I have to replace
the database with previous night database.

I have tried to open the database and close the database just in case a
user has closed the database inappropriate, but the ldb file is still
visible.

I have tried to open the ldb file with notepad to see which users are
using the database, but the users that are shown in notepad have left
and they have nor remote access.

How can I close the ldb file to have exclusive access to the database
to make changes and no to get errors the following day using the
database?

Regards

John

[Thilo Immel]

John,

I have encountered a problem with the ldb file of a database. When
making changes to the backend databases I need exclusive access to make
changes. I usually do this at night when all users have left the premises,
but for the last couple of nights there are no users using the database
and the ldb file is still visible even though I'm sure nobody is using
the database. I have tried to manually delete the lbd file but the
following day users encountered problems with database so I have to replace
the database with previous night database.

I have tried to open the database and close the database just in case a
user has closed the database inappropriate, but the ldb file is still
visible.

I have tried to open the ldb file with notepad to see which users are
using the database, but the users that are shown in notepad have left
and they have nor remote access.
This is by design and so it's quite normal.
How can I close the ldb file to have exclusive access to the database
to make changes and no to get errors the following day using the
database?

Delete the ldb file. This will NOT cause any problems the following
day. But the problems and the not deleted ldb file have the same
reason: someone has left the MDB file not properly.

Have a look at Tonys page: www.granite.ab.ca/access/corruptmdbs.htm

Regards

Thilo Immel
Access Repair Service www.atroplan.com
NEW: Access Memory Reporter 1.0
Shows the use of memory by tables and indexes.

[Tony Toews]

jn**********@yahoo.com (John) wrote:

I have encountered a problem with the ldb file of a database. When
making changes to the backend databases I need exclusive access to make
changes. I usually do this at night when all users have left the premises,
but for the last couple of nights there are no users using the database
and the ldb file is still visible even though I'm sure nobody is using
the database. I have tried to manually delete the lbd file but the
following day users encountered problems with database so I have to replace
the database with previous night database.
What kind of problems?
I have tried to open the database and close the database just in case a
user has closed the database inappropriate, but the ldb file is still
visible.
That should've deleted the LDB.
I have tried to open the ldb file with notepad to see which users are
using the database, but the users that are shown in notepad have left
and they have nor remote access.

This is normal behaviour.

Opening the .ldb file using notepad will show you both who's currently in the
database and some of the workstations which were in the database. When a person
exits Access their workstation name and Access login id, Admin unless you are using
Access security, are left in a "slot" or record in the ldb file. This slot or record
may get overwritten the next time someone enters the MDB depending on what slot or
record is available previous to it in the ldb file.

Determining the workstation which caused the Microsoft Access MDB corruption
http://www.granite.ab.ca/access/corr...orkstation.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[John]

Hi All,

I have tried to remove the ldb files of the backend databases but the
ldb file returns immediately. I'm more than sure than no one is using
the database. I want to make a few changes to the backend databases
but I can't because I get a message that I don't have exclusive access
when no one is using the database.

I have tried several times to delete the ldb file but it keeps
appearing. Has anyone experienced this problem before??

Regards

John

Tony Toews <tt****@telusplanet.net> wrote in message news:<i4********************************@4ax.com>. ..

jn**********@yahoo.com (John) wrote:

I have encountered a problem with the ldb file of a database. When
making changes to the backend databases I need exclusive access to make
changes. I usually do this at night when all users have left the premises,
but for the last couple of nights there are no users using the database
and the ldb file is still visible even though I'm sure nobody is using
the database. I have tried to manually delete the lbd file but the
following day users encountered problems with database so I have to replace
the database with previous night database.

What kind of problems?

I have tried to open the database and close the database just in case a
user has closed the database inappropriate, but the ldb file is still
visible.

That should've deleted the LDB.

I have tried to open the ldb file with notepad to see which users are
using the database, but the users that are shown in notepad have left
and they have nor remote access.

This is normal behaviour.

Opening the .ldb file using notepad will show you both who's currently in the
database and some of the workstations which were in the database. When a person
exits Access their workstation name and Access login id, Admin unless you are using
Access security, are left in a "slot" or record in the ldb file. This slot or record
may get overwritten the next time someone enters the MDB depending on what slot or
record is available previous to it in the ldb file.

Determining the workstation which caused the Microsoft Access MDB corruption
http://www.granite.ab.ca/access/corr...orkstation.htm

Tony

[Tony Toews]

jn**********@yahoo.com (John) wrote:

I have tried to remove the ldb files of the backend databases but the
ldb file returns immediately. I'm more than sure than no one is using
the database. I want to make a few changes to the backend databases
but I can't because I get a message that I don't have exclusive access
when no one is using the database.

I have tried several times to delete the ldb file but it keeps
appearing. Has anyone experienced this problem before??

Something is definitely recreating the LDB file. Have you tried opening it in
notepad and seeing if there are any clues in there such as workstation name? Do not
save it though.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[John]

Hi Tony,
I have opened the ldb file in notepad which displays the workstations
and users, but these users and workstations are not longer using the
database. I have physically checked the users and workstations.

I do not know what is recreating the ldb file. Do you have any ideas
what is behind it??

Regards

John

Tony Toews <tt****@telusplanet.net> wrote in message news:<3l********************************@4ax.com>. ..

jn**********@yahoo.com (John) wrote:

I have tried to remove the ldb files of the backend databases but the
ldb file returns immediately. I'm more than sure than no one is using
the database. I want to make a few changes to the backend databases
but I can't because I get a message that I don't have exclusive access
when no one is using the database.

I have tried several times to delete the ldb file but it keeps
appearing. Has anyone experienced this problem before??

Something is definitely recreating the LDB file. Have you tried opening it in
notepad and seeing if there are any clues in there such as workstation name? Do not
save it though.

Tony

[Julia Baresch]

I've had problems with the .ldb file hanging up, and one of our server
people is able to check and see who actually still has the database
open. Do you have anyone who can do that?

Since it keeps being re-created, someone or something must be
connecting to it. Is anyone using merge files that pull data from it?
That will create an .ldb file also.

jn**********@yahoo.com (John) wrote in message news:<b5**************************@posting.google. com>...

Hi Tony,
I have opened the ldb file in notepad which displays the workstations
and users, but these users and workstations are not longer using the
database. I have physically checked the users and workstations.

I do not know what is recreating the ldb file. Do you have any ideas
what is behind it??

Regards

John

Tony Toews <tt****@telusplanet.net> wrote in message news:<3l********************************@4ax.com>. ..

jn**********@yahoo.com (John) wrote:

I have tried to remove the ldb files of the backend databases but the
ldb file returns immediately. I'm more than sure than no one is using
the database. I want to make a few changes to the backend databases
but I can't because I get a message that I don't have exclusive access
when no one is using the database.

I have tried several times to delete the ldb file but it keeps
appearing. Has anyone experienced this problem before??

Something is definitely recreating the LDB file. Have you tried opening it in
notepad and seeing if there are any clues in there such as workstation name? Do not
save it though.

Tony

[Tony Toews]

jn**********@yahoo.com (John) wrote:

I have opened the ldb file in notepad which displays the workstations
and users, but these users and workstations are not longer using the
database. I have physically checked the users and workstations.

I do not know what is recreating the ldb file. Do you have any ideas
what is behind it??

No. But what is confusing to me is that you delete the ldb file, which you couldn't
do if anyone was in the MDB as well, and a few minutes later the ldb file is back but
with some users and workstations in it. The only way that the ldb can be recreated
with that data is by those users/workstations.

Or somehow, and this is highly unlikely, something is restoring that file from
somewhere.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[John]

Hi Tony,
To be honest I have no idea what is recreating the ldb file. I will
probably copy the backend databases to another folder, make all the
require changes then copy the databases back to the appropriate
folder.

I don't believe this will corrupt the database. Would it??

Regards

John

Tony Toews <tt****@telusplanet.net> wrote in message news:<ci********************************@4ax.com>. ..

jn**********@yahoo.com (John) wrote:

I have opened the ldb file in notepad which displays the workstations
and users, but these users and workstations are not longer using the
database. I have physically checked the users and workstations.

I do not know what is recreating the ldb file. Do you have any ideas
what is behind it??

No. But what is confusing to me is that you delete the ldb file, which you couldn't
do if anyone was in the MDB as well, and a few minutes later the ldb file is back but
with some users and workstations in it. The only way that the ldb can be recreated
with that data is by those users/workstations.

Or somehow, and this is highly unlikely, something is restoring that file from
somewhere.

Tony

[Tony Toews]

jn**********@yahoo.com (John) wrote:

To be honest I have no idea what is recreating the ldb file. I will
probably copy the backend databases to another folder, make all the
require changes then copy the databases back to the appropriate
folder.

I don't believe this will corrupt the database. Would it??

It could if a user was in the MDB doing an update. Besides you'd lose the changes
they made. I'd suggest renaming except you're are still going to have the problem
of figuring out what user(s) are locking the mdb. You can also get the system
admins to figure out who has a file lock on the file.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm