Access97 instance stuck in memory

G

Gary D.

In one of my applications, whenever I close the database (or Access
completely), I get an instance of Access "stuck" in memory, with the
Access window minimized onto the task bar. If I click on the icon the
window becomes resized and is still available although no database is
open. Also, the SYSTEM.ldb file gets left behind, along with
(sometimes) the ldb for the specific application mdb file.

I've had this before and discovered it was because I had not released
resources in VBA (Set *** = Nothing). However, in this troublesome
application I have checked and all resources are released (all
recordsets and database instances are closed then set to nothing).

Is there a way I could determine what it being left behind, if
anything, or what else might be causing this?


PS. I'm using Access97 on Windows98.
 
A

Allen Browne

If all recordsets that you open are being closed and set to Nothing, the
other cause of this behavior was referring to a boolean control like this:
If Me.MyCheckBox Then

Access would sometimes fail to release this reference.
Workarounds:
If Me.MyCheckBox.Value Then
If (Me.MyCheckBox) Then
If Me.MyCheckBox = True Then
 
G

Gary D.

If all recordsets that you open are being closed and set to Nothing, the
other cause of this behavior was referring to a boolean control like this:
If Me.MyCheckBox Then

Access would sometimes fail to release this reference.
Workarounds:
If Me.MyCheckBox.Value Then
If (Me.MyCheckBox) Then
If Me.MyCheckBox = True Then

Thanks Allen

I've made some changes and so far it seems to be working (although the
problem is sporadic - I'll let you know if it happens again).

Gary
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top