MSACCESS.EXE does not stop after exiting Access 2003

[mcglincym]

Occasionally, the MSACCESS.EXE process does not stop after I exit Access. The
process shows about 50% CPU usage in Windows Task Manager. Sometimes memory
usage increases slowly but not always. As far as I can tell, there is nothing
going on before I exit.

 

[Chris Mills]

I presume you mean "stays on the taskbar".

Various programming "bugs" (actually I think they are Access bugs) can cause
this, and they can be a right pig to find.

See:
http://www.mvps.org/access/bugs/bugs0005.htm

Also (I don't see it listed there) I'm under an impression that:
If Something Then
....instead of...
If Something = True Then
....can cause this bug. Or some bug.
(well, I'm thinking back to A97 whatever)

Chris

 

[mcglincym]

Access does not show on the taskbar, only under Task Manager. Also, I usually
close an open database before exiting Access and some of my databases do not
include any code at all. I'll read the reference.

 

[Douglas J. Steele]

You're not doing anything funky like using Automation to open another
session of Access, are you?

 

[mcglincym]

I am checking for any objects not closed and set to nothing as suggested in
the link posted by Chris Mills. I use one database as a library and reference
it from other databases with forms. My library procedures use a browse dialog
from the Office Object library, statistical functions from the Excel Object
library, and a declared HTMLHelp function from HHCtrl.ocx. I think that I no
longer use Automation of Access but I'll check.

 

[Gordon Clark]

I'm running into the same issue - haven't heard from any users if this is
happening to them, as of yet. What happens is after the screensaver mode
kicks in and I'm logged off the machine (XP relogon to network/machine), I'll
key in my password, opening to Desktop, and the VBA project window will be
open - stating "No open projects" on the title bar. I've seen as many as
four instances of MSACCESS.exe running concurrently in Taskman on these
occurences.

The VBA window does occupy the taskbar normally, with the application name
in the titlebar. Close that, open Taskman, and still find the four instances
running 'behind the scenes'.

What I haven't done = to check for instances running where I may not see the
VBA window....

On DAO - not really using that - there is perhaps use of at least one
RecordsetClone, but that usage is buried deep in the code of an infrequently
used form.

Your mention of implicit "If Something = True Then..." is definitely
something I can check for, I do like to save a keystroke where possible *eek*.

Platform is XP Pro, Access 2002, native 2002 version DB.

Thank you for your previous inputs - looks like I've got some homework to
do.... =(.

Gordon

 

[Chris Mills]

Be interested in the Original Poster saying what they found, if anything?
-----
Gordon,
Thanks for feedback. I can't check all that. I use power-save for monitor not
screensaver, but even when I do (1 min, as long as I can sit idle!) I see no
problems with A2002/Win98gulp. I don't have WinXP so I can't really verify
what you say. If you can reproduce it consistently as you stated, then it
sounds like yet another bug?
(it would be no fun without them?)

But it's worth following-up the documented causes first I think (Access Web I
think, not MS)

The "If Something = True" was experienced by me (I think) but not discovered
or made up by me, I found this possible cause on The Access Web. A colleague
of mine with a BSc degree said "of course you should specify =TRUE", but I say
B.S. that's a bug because you don't have to specify, for instance, in C, or
any language other than Access (anything sensible!!!).

Cheers
Chris

PS if it's some other bug, don't expect MS to fix it, they are famous for not
bothering to fix known bugs, instead you have to know of a workaround to avoid
it.