Use of ldb File ??

[Mike Thomas]

We are using an Access 2000 app on a Citrix server with Windows 2000. There
are between 3 and 12 people using it in a typical day. I've noticed that
when everybody has closed their apps (at least in theory) the ldb file is
still there, it cannot be deleted, and the application cannot be edited in
any way. Usually, after rebooting the server, this file can be erased
(sometimes it cannot be erased). ALso, the application can be edited.

What does this file do ?

Should it always be closed automatically when the last user exits the
application. Eg, is Access that smart to be able to figure out to close it?

Finally, is there a way to know when the last user is exiting? I'd like to
do a compact and repair on the back end data mdb.

Many thanks
Mike Thomas

[Rick Brandt]

"Mike Thomas" <Mi******@Yahoo.com> wrote in message
news:nE**********************@newssvr28.news.prodi gy.com...

We are using an Access 2000 app on a Citrix server with Windows 2000. There are between 3 and 12 people using it in a typical day. I've noticed that
when everybody has closed their apps (at least in theory) the ldb file is
still there, it cannot be deleted, and the application cannot be edited in any way. Usually, after rebooting the server, this file can be erased
(sometimes it cannot be erased). ALso, the application can be edited.

What does this file do ?

Should it always be closed automatically when the last user exits the
application. Eg, is Access that smart to be able to figure out to close it?
Finally, is there a way to know when the last user is exiting? I'd like to do a compact and repair on the back end data mdb.

Do users have file delete privileges on the folder? If not the LDB won't
get deleted. Otherwise the file not auto-deleting is usually caused by
someone having an improper exit from the MDB. Perhaps you have users who
are ending their Citrix sessions without logging off first?

Even with Citrix users should not share a common front end file. Is that
what you have?
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Trev]

"Mike Thomas" <Mi******@Yahoo.com> wrote in message
news:nE**********************@newssvr28.news.prodi gy.com...

We are using an Access 2000 app on a Citrix server with Windows 2000. There are between 3 and 12 people using it in a typical day. I've noticed that
when everybody has closed their apps (at least in theory) the ldb file is
still there, it cannot be deleted, and the application cannot be edited in
any way. Usually, after rebooting the server, this file can be erased
(sometimes it cannot be erased). ALso, the application can be edited.

What does this file do ?
Holds lock info for logged in users.
Should it always be closed automatically when the last user exits the
application. Eg, is Access that smart to be able to figure out to close

it?

Yes, Access will delete the file upon exit, all but the last one out will
fail to delete the file.

[Sharon]

"Mike Thomas" <Mi******@Yahoo.com> wrote in message news:<nE**********************@newssvr28.news.prod igy.com>...

when everybody has closed their apps (at least in theory) the ldb file is
still there, it cannot be deleted, and the application cannot be edited in
any way.

Those blasted lbd's are the source of much mischief. I don't know the
answer to all your questions, but I do know how to get rid of those
lbd's without re-booting. Press Ctrl+Alt+Del to open Task Manager. On
the Processes tab end every MSACCESS.EXE process you can find (you can
sort by clicking on column heads). Often there are several. I do know
that I read (some time ago) several articles about those lbd's causing
problems and have since adopted a standard procedure of having an
ever-loaded form (a switchboard, for instance) which keeps a
connection to the backend open at all times. This has eliminated soooo
many problems. BTW, lbd means "locked database". That gives a hint
about what it's for. It just seems to want to hang around long after
the party's over.

[Not Me]

"Mike Thomas" <Mi******@Yahoo.com> wrote in message
news:nE**********************@newssvr28.news.prodi gy.com...

Finally, is there a way to know when the last user is exiting? I'd like to do a compact and repair on the back end data mdb.

The file ldbview may be useful to you, (find it on microsoft.com) it shows
who's logged into the database and when they come out it should flash up
that this has happened - of course only if everyone's closing down properly
:)

HTH,
Chris