Access consumes 100percent cpu usage!

[petrosky]

Hi,

Computer running 3Ghz, 1 gig ram...XP Pro SP2.

I create even a blank database and cpu usage quickly rises to 100 percent. After about a minute of no activity it drops back down to basically zero but climbs again even if I simply select the query tab!

I have uninstalled/reinstalled but the problem still exists.

I have searched micro$oft KB but to no avail.

Does anyone have any ideas where I should start?

TIA.

Peter

Remember- It's nice to be important,
but it's important to be nice

 

[PHV]

Just a though:
menu Tools -> Options -> tab General: deselect all the autocorrect options.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[jsteph]

Peter,
I've asked this same thing here before, and the answer I got was basically "it's no big deal". I don't buy this, even if it's only using up 'idle' cycles.

And that's what it seems to be doing--using 'idle' cycles. In other words, as soon as you run something else, it immediatly and without contention gives up the cycles. UNLESS, of course it's actually doing 'something', such as running a query--this is when Access, being an MS product, pulls rank and refuses other apps a slice until it damn well pleases.

But what I've noticed about the 'idle' cycles that it consumes is that it's not NOOP loops--it's doing something because I have a cpu temp meter and it the temp goes up significantly when Access is 'doing nothing'.

Bottom line--this is something of which MS is keenly aware. Whether it's a bug or not, I don't know. And though MS will definitely not speak to this at all, don't be fooled if they act like they don't know what you're talking about--they know damn well what's going on here.
--Jim

 

[petrosky]

Hi,

Thanks for the idea PHV but it's still peaking out.

Jim, the truth is I would never have noticed this if I didn't have the task manager open for another purpose.

I guess what shocked me was that even when I created a new DB, the issue seemed the same as when opening/working with much larger DBs.

Interesting reading.

Peter

Remember- It's nice to be important,
but it's important to be nice

 

[lupins46]

Given that this IS normal behaviour for Access and it does not disrupt other processes, why are you concerned?

 

[jsteph]

Consistent with repsponses from previous posts such as "it's no big deal"

Given that this IS normal behaviour for Access and it does not disrupt other processes, why are you concerned?

lupins46
It IS a big deal.

cpu temp meter and it the temp goes up significantly when Access is 'doing nothing'

Sure, if it's in the pseudo 'idle' state but consuming 99% of cpu, it will give it up to the another process, but it's wear & tear that I don't need nor want. What you're saying is like saying "So what if you're car idles at 5000 rpm?"
--Jim

 

[grnzbra]

That doesn't seem right. I just tried it. When I signed in, it used 3% and when I ran a query it used 5%. On large action queries that took 30 minutes to run, I've seen it suck up just about all the cpu but what you're describing doesn't seem right.

Unfortunately, I don't have a solution for you.

 

[jsteph]

In my experience, it seems to have something to do with ODBC, it seems to do this when and ODBC table or query is open and it's not the odbc-refresh option, as far as I can tell, though it could have something to do with the odbc-driver itself--it may be in a constant conversation with the server as long as the connection is established.

I don't think I've done a 'pure access' app in years, they all have a SQL backend of some sort, so I see this all the time.
--Jim