Why is Access using cpu cycles when 'idle'?

[jsteph]

I asked this before in thread181-814758, and never got a real answer, I'm wondering if maybe there are any new experts who may have some deep knowledge of the inner-workings of Access.

Basically, the task manager shows 100% cpu when Access is just sitting there, say with a datasheet open. No code running, just sitting there. What is it doing with those cycles? I know that Access, due to nepotism, has rights to the inner-ring os/cpu-cycles that other apps might not. That I can deal with--my question is: What is it doing? If it's doing 'nothing', then the cpu wouldn't be at 100%. I know it occasionally refreshes the datasheet--ok, a few milliseconds, if that. Why peg the meter when doing nothing?

It's a real problem because my cpu-temp alarm would go off when I was away from the box and nothing was running--except an 'idle' msaccess app. I just don't like heating the cpu constantly when it should be idling.

The other process that pegs the cpu is that darn 'system idle process'. How do I kill that? (I'm just kidding about that one--relax).
--Jim

 

[psemianonymous]

Access is using spare cycles, as in--it doesn't use 100% of the CPU, but if no one else is using it--hey, why not? In short: the task manager is lying to you. So I know the what (Task Manager is a liar), if not the why (Why the Task Manager is a liar).

If you want to ask the true Access internals experts, post this on comp.databases.ms-access, or search Google Groups for similar existing topics. My guess: no one cares why. Sorry about your odd CPU beeping error--this is a feature, not a bug, so you're going to have to work around this 'feature' forever.


Pete

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[jsteph]

Pseale,
Thanks for replying. Yes, in actuality it probably isn't a practical problem because Access gives back control to whatever else needs to run. However, I should have been more clear--MSAccess.exe isn't using the whole 100%, there are a few other minor things using a few percent, but task manager reports access using about 95%, If I open two instances, they split the 95% somewhat evenly.

Anyway, I'll check the sites you mentioned because it's really become more of an academic issue with me, although the cpu staying hot (and I know the temp meter is not lying) is of some concern.
--Jim