|
 |
access thread: Access thread running after Database closed
Message #1 by luckychap@b... on Tue, 11 Dec 2001 10:23:03
|
|
I have an Access data base used on a network by several users. On closing
(docmd.quit), it leaves an instance of access running and inactive. It can
be seen on the task , and the only way of removing it is with task manager
or "control alt delete". The instance can prevent the record locking file
(.ldb) from closing. I am using NT but other users have the same problem
with all Windows operating systems from 95 to 2000. The application can
have up to four screens open at the same time. I have tried cycling
through and closing everything in the screens collection and every work
space is closed. I would really appreciate talking to someone who has had
the same problem or knows the answer.
David
Message #2 by brian.skelton@b... on Tue, 11 Dec 2001 12:33:13
|
|
David
This is a known bug, generally caused when a DAO object is left. Have a
look here for a full description:
http://www.mvps.org/access/bugs/bugs0005.htm
As it says in the article, it's not an easy bug to track down. The only
sure solution is to go through every line of code and ensure you
explicitly close all objects.
-Brian
> I have an Access data base used on a network by several users. On
closing
> (docmd.quit), it leaves an instance of access running and inactive. It
can
> be seen on the task , and the only way of removing it is with task
manager
> or "control alt delete". The instance can prevent the record locking
file
> (.ldb) from closing. I am using NT but other users have the same problem
> with all Windows operating systems from 95 to 2000. The application can
> have up to four screens open at the same time. I have tried cycling
> through and closing everything in the screens collection and every work
> space is closed. I would really appreciate talking to someone who has
had
> the same problem or knows the answer.
> David
Message #3 by "David Chapman" <luckychap@b...> on Wed, 12 Dec 2001 18:55:34 +1030
|
|
Thanks Brian,
I will get back to work and hopefully will be able to persuade my loyal
users to put their guns away
David
----- Original Message -----
From: <brian.skelton@b...>
To: "Access" <access@p...>
Sent: Tuesday, December 11, 2001 12:33 PM
Subject: [access] Re: Access thread running after Database closed
> David
>
> This is a known bug, generally caused when a DAO object is left. Have a
> look here for a full description:
>
> http://www.mvps.org/access/bugs/bugs0005.htm
>
> As it says in the article, it's not an easy bug to track down. The only
> sure solution is to go through every line of code and ensure you
> explicitly close all objects.
>
> -Brian
>
> > I have an Access data base used on a network by several users. On
> closing
> > (docmd.quit), it leaves an instance of access running and inactive. It
> can
> > be seen on the task , and the only way of removing it is with task
> manager
> > or "control alt delete". The instance can prevent the record locking
> file
> > (.ldb) from closing. I am using NT but other users have the same problem
> > with all Windows operating systems from 95 to 2000. The application can
> > have up to four screens open at the same time. I have tried cycling
> > through and closing everything in the screens collection and every work
> > space is closed. I would really appreciate talking to someone who has
> had
> > the same problem or knows the answer.
> > David
|
|
|
View Cart
