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.
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.