By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,701 Members | 2,006 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,701 IT Pros & Developers. It's quick & easy.

Problem With Access Not Closing Properly

P: n/a
I have had a problem for some time with several databases and figure
there must be a common underlying cause. Sometimes when I open a
database, nothing appears to happen, but an .ldb file gets created and
Access is running in Task Manager. No sign of Access on the screen or
Taskbar though.

Today, I've partly figured out what is happening. Sometimes when in
design mode, I'll be opening and closing forms and after I close the
last form, I'll close Access itself. Sometimes, but not always, an
instance of Access is left running in Task Manager. I assume that the
database has closed properly because the .ldb file disappears.

Then the next time I try to open a database (with the instance of
Access still running in Task Manager) the problem described in the
first paragraph above appears.

What scenarios would cause Access to be left running in Task Manager,
but at the same time the .ldb file is closed?
Nov 7 '08 #1
Share this Question
Share on Google+
8 Replies


P: n/a
What version of Access is this?

There was a problem like that back in A97. Essentially, there were a couple
of objects that were not being automatically released: recordsets that were
not explicitly closed and set to nothing, and boolean controls (check box,
option button, toggle button) that were referenced directly without
explicitly forcing Value to be read.

If that's not it, remove any library references you don't need (so it's not
a DLL or OCX issue.) If you have any class modules, make sure you explicitly
de-reference.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Wayne" <cq*******@volcanomail.comwrote in message
news:27**********************************@w24g2000 prd.googlegroups.com...
>I have had a problem for some time with several databases and figure
there must be a common underlying cause. Sometimes when I open a
database, nothing appears to happen, but an .ldb file gets created and
Access is running in Task Manager. No sign of Access on the screen or
Taskbar though.

Today, I've partly figured out what is happening. Sometimes when in
design mode, I'll be opening and closing forms and after I close the
last form, I'll close Access itself. Sometimes, but not always, an
instance of Access is left running in Task Manager. I assume that the
database has closed properly because the .ldb file disappears.

Then the next time I try to open a database (with the instance of
Access still running in Task Manager) the problem described in the
first paragraph above appears.

What scenarios would cause Access to be left running in Task Manager,
but at the same time the .ldb file is closed?
Nov 7 '08 #2

P: n/a
On Nov 7, 5:08*pm, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
What version of Access is this?

There was a problem like that back in A97. Essentially, there were a couple
of objects that were not being automatically released: recordsets that were
not explicitly closed and set to nothing, and boolean controls (check box,
option button, toggle button) that were referenced directly without
explicitly forcing Value to be read.

If that's not it, remove any library references you don't need (so it's not
a DLL or OCX issue.) If you have any class modules, make sure you explicitly
de-reference.

--
Allen Browne - Microsoft MVP. *Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
Thanks for the reply Allen. I'm using A2003. I'll follow your advice
and see how I go.
Nov 7 '08 #3

P: n/a
Hi Allen

Could you be more specific about De-Referencing Class modules. Something
I've never done.
Should it always be done. I presume it is nothing more than setting the
MyClass = Nothing as the end of a procedure

Tanks

Phil
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:49***********************@per-qv1-newsreader-01.iinet.net.au...
What version of Access is this?

There was a problem like that back in A97. Essentially, there were a
couple of objects that were not being automatically released: recordsets
that were not explicitly closed and set to nothing, and boolean controls
(check box, option button, toggle button) that were referenced directly
without explicitly forcing Value to be read.

If that's not it, remove any library references you don't need (so it's
not a DLL or OCX issue.) If you have any class modules, make sure you
explicitly de-reference.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Wayne" <cq*******@volcanomail.comwrote in message
news:27**********************************@w24g2000 prd.googlegroups.com...
>>I have had a problem for some time with several databases and figure
there must be a common underlying cause. Sometimes when I open a
database, nothing appears to happen, but an .ldb file gets created and
Access is running in Task Manager. No sign of Access on the screen or
Taskbar though.

Today, I've partly figured out what is happening. Sometimes when in
design mode, I'll be opening and closing forms and after I close the
last form, I'll close Access itself. Sometimes, but not always, an
instance of Access is left running in Task Manager. I assume that the
database has closed properly because the .ldb file disappears.

Then the next time I try to open a database (with the instance of
Access still running in Task Manager) the problem described in the
first paragraph above appears.

What scenarios would cause Access to be left running in Task Manager,
but at the same time the .ldb file is closed?

Nov 7 '08 #4

P: n/a
On Thu, 6 Nov 2008 21:03:01 -0800 (PST), Wayne
<cq*******@volcanomail.comwrote:

I've seen this happen if DAO or ADO objects are not properly closed
and disposed of.
And when people refuse to be on the latest service packs.

-Tom.
Microsoft Access MVP

>I have had a problem for some time with several databases and figure
there must be a common underlying cause. Sometimes when I open a
database, nothing appears to happen, but an .ldb file gets created and
Access is running in Task Manager. No sign of Access on the screen or
Taskbar though.

Today, I've partly figured out what is happening. Sometimes when in
design mode, I'll be opening and closing forms and after I close the
last form, I'll close Access itself. Sometimes, but not always, an
instance of Access is left running in Task Manager. I assume that the
database has closed properly because the .ldb file disappears.

Then the next time I try to open a database (with the instance of
Access still running in Task Manager) the problem described in the
first paragraph above appears.

What scenarios would cause Access to be left running in Task Manager,
but at the same time the .ldb file is closed?
Nov 7 '08 #5

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalidwrote in
news:49***********************@per-qv1-newsreader-01.iinet.net.au:
There was a problem like that back in A97.
The idea that this problem went away after A97 is news to me.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Nov 8 '08 #6

P: n/a
On Fri, 7 Nov 2008 13:45:40 -0000, "Phil Stanton"
<ph**@myfamilyname.co.ukwrote:

That *is* dereferencing.
-Tom.

>Hi Allen

Could you be more specific about De-Referencing Class modules. Something
I've never done.
Should it always be done. I presume it is nothing more than setting the
MyClass = Nothing as the end of a procedure

Tanks

Phil
"Allen Browne" <Al*********@SeeSig.Invalidwrote in message
news:49***********************@per-qv1-newsreader-01.iinet.net.au...
>What version of Access is this?

There was a problem like that back in A97. Essentially, there were a
couple of objects that were not being automatically released: recordsets
that were not explicitly closed and set to nothing, and boolean controls
(check box, option button, toggle button) that were referenced directly
without explicitly forcing Value to be read.

If that's not it, remove any library references you don't need (so it's
not a DLL or OCX issue.) If you have any class modules, make sure you
explicitly de-reference.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Wayne" <cq*******@volcanomail.comwrote in message
news:27**********************************@w24g200 0prd.googlegroups.com...
>>>I have had a problem for some time with several databases and figure
there must be a common underlying cause. Sometimes when I open a
database, nothing appears to happen, but an .ldb file gets created and
Access is running in Task Manager. No sign of Access on the screen or
Taskbar though.

Today, I've partly figured out what is happening. Sometimes when in
design mode, I'll be opening and closing forms and after I close the
last form, I'll close Access itself. Sometimes, but not always, an
instance of Access is left running in Task Manager. I assume that the
database has closed properly because the .ldb file disappears.

Then the next time I try to open a database (with the instance of
Access still running in Task Manager) the problem described in the
first paragraph above appears.

What scenarios would cause Access to be left running in Task Manager,
but at the same time the .ldb file is closed?
Nov 8 '08 #7

P: n/a
Wayne <cq*******@volcanomail.comwrote:
>Today, I've partly figured out what is happening. Sometimes when in
design mode, I'll be opening and closing forms and after I close the
last form, I'll close Access itself. Sometimes, but not always, an
instance of Access is left running in Task Manager. I assume that the
database has closed properly because the .ldb file disappears.

Then the next time I try to open a database (with the instance of
Access still running in Task Manager) the problem described in the
first paragraph above appears.
Yes, this happens to me occasionally as well when developing. Never to clients
though. Although maybe some have figured out to reboot without mentioning anything
to me. <smile>

I suspect it's happening because I hit a Stop command and then halt the code without
closing a recordset. Or something like that.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Nov 9 '08 #8

P: n/a
Also search for "never ending Access" in this group and the obscure
one that got me:

"Info: Another cause of never ending Access window"

Cheers
Terry
Nov 10 '08 #9

This discussion thread is closed

Replies have been disabled for this discussion.