Access 2007 on XP: Slow, Glitchy and Maddening

[Mark Olbert]

I'm interested in hearing if anyone else is having these kinds of problems running Access 2007 under XP (SP2), on a 2.4GHz Pentium 4
having 1GB of RAM and no other applications running:

- sluggish behavior on opening objects (e.g., tables, queries)

- frequent lengthy "timeouts" when trying to do things like right-click to bring up a context menu, or change the width of a column
in an sproc query (this almost feels like the delay-to-load things you'd notice in Access XP when it was pausing to load a DLL)

I had Task Manager open during some of this time, and never saw the Access process' CPU utilization go above 20% (I only saw it
spike above the 10% level for a couple of brief moments).

Frankly, based on my experience so far, this "upgrade" has been a major disappointment. Sure, the new UI is nice (and I like being
able to connect to SqlServer 2005 backends), but what good is it if after 10 minutes of use I want to start ripping my hair out in
frustration?

FWIW, I've noticed similar glitchiness in Excel 2007, too (I haven't used Word 2007 enough to tell).

- Mark

 

[Guest]

I have a somewhat less powerful computer than yours but haven't noticed the
performance same problems.

When you open up Task Manager, what is taking up the CPU? Try sorting on the
CPU column of the Processes tab.

Have you tried disabling the Virus Checker software for testing? I've seen a
couple of things about AVG and 2007 having problems.

Of course running your virus checker and spyware checker with fresh
signature files might show that 2007 isn't the problem.

 

[Mark Olbert]

Jerry,

Access 2007 is the second highest CPU user, behind the System Idle process.

Turning off my antivirus software (NOD32, from ESET) did seem to improve things. I'll play around with that a bit more.

- Mark

 

[Guest]

Most virus scanners allow you to exclude certain file types such as .mdb or
..md* or .md?.

Actually Access having only the second highest CPU is nice. Older versions
of Access would often peg the CPU at 99%. From what I gather this was mostly
a bad reading and Access would give up CPU time as soon as any other program
needed it.