I have a front end Access 2000 mde linking to a back end 2000 mdb. It
is currently running happily on hundreds of client's PCs, both single
and networked. On my own Win 7 PC, it runs fine in Acc 2007 or 2010.
On one client PC (Win 7) running Access 2007 runtime, it is very slow
to relink the back end tables, even when the tables reside on the
local PC. While it is relinking, the memory usage goes up from around
80MB to over 1GB and the CPU usage to 50-60%. Eventually the relinking
is successful, but then moving between tabs on a form takes 30
seconds, instead of its normal instantaneous rate. The performance
varies from one back end to the next, but is generally poor. I have
tried all the standard solutions, and so has my IT guy, short of
buying a new PC. This is a new PC with lots of memory, processing
power and disk space. Any suggestions?

Owen

What Antivirus are you using? Norton 360 made my Access applications almost
unusable until I turned off the live scanning. All others I could exclude
MDB and LDB from the scans, to fix the problem.




"Owen" wrote in message
news:ac017d2d-a59d-427f-9b29-4afd3eeceea3 (AT) a28g2000prb (DOT) googlegroups.com...

I have a front end Access 2000 mde linking to a back end 2000 mdb. It
is currently running happily on hundreds of client's PCs, both single
and networked. On my own Win 7 PC, it runs fine in Acc 2007 or 2010.
On one client PC (Win 7) running Access 2007 runtime, it is very slow
to relink the back end tables, even when the tables reside on the
local PC. While it is relinking, the memory usage goes up from around
80MB to over 1GB and the CPU usage to 50-60%. Eventually the relinking
is successful, but then moving between tabs on a form takes 30
seconds, instead of its normal instantaneous rate. The performance
varies from one back end to the next, but is generally poor. I have
tried all the standard solutions, and so has my IT guy, short of
buying a new PC. This is a new PC with lots of memory, processing
power and disk space. Any suggestions?

Owen

Hi Ron. Thanks, but I've already tried disabling Norton. After more
testing today, I found that if I create a new database (mdb or accdb)
in Access 2007 and import a table from the backend database, it is
incredibly slow to open the table. That is, it takes about 2-3 min to
open the table. It contains about 5000 records and is on the local
drive, not the network. Importing the table only took a few seconds,
but opening it was the problem. I've uninstalled all office programs
and reinstalled just Access 2007, and still get the same result. The
same happens with Access 2010. Interestingly, with Access 2003, the
speed is fast on the local PC, but slows to a crawl on the network.
However, it's not intrinsically a network problem, since the same
occurs with Access 2007/2010 on the local drive. My next plan is to
run some hardware diagnostics and reinstall Window 7.

Owen

Well, it was Norton after all! Disabling it did nothing, but
uninstalling it solved the problem. Reinstalling it, even with the
scanning disabled, slowed the db to an unusable state. Norton is
looking into it.

Owen

If you must use Norton, try moving up to SEP. Otherwise try Microsoft
security essentials. It's free and after excluding Access files it worked
OK.

Here is another followup ...

Turns out it wasn't a problem with Norton, it was the HP SimplePass
Identity Protection that was installed by default on the new HP
machine. Uninstalling this fixed the problem, and then there was no
problem with Norton. I have just had a similar problem with another
client where several tables would not open, and Access just froze
without showing a single record (tables on local drive). Removing HP
SimplePass fixed this too. I can see I'll have to warn new clients
about this problem.

Owen

On Tue, 22 Feb 2011 17:05:38 -0800 (PST), Owen
<google (AT) healthbase (DOT) com.au> wrote:

Whoa, that's very interesting. Thanks for posting.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

Definitely appreciated. Thanks for the heads-up.

The Frog

The Frog <mr.frog.to.you (AT) googlemail (DOT) com> wrote in
news:eea3d52b-0b16-4786-adc8-6074bbc64a32 (AT) a5g2000vbs (DOT) googlegroups.com
:

I'd sure love to hear an explanation of why it interfered with
Access performance.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

I learned a long time ago never to ask HP anything even slightly
technically related. The call centres are staffed by script reading
non-technical people. The reps are nice people but all charm and no
technical substance for the most part. The internal tech support is
mostly made up of ex retail sales people who have some familiarity
with their products. My guess is the reason it interferes is that it
is a minimum effort bloatware product that really isnt a well
developed piece of software - like a lot of the HP software. HP
probably dont even know what it is really doing, they only care that
the intended job is done - collateral damage so-to-speak is not a
concern of theirs, nor is performance or integration with anything
other than other HP items. Dont get me wrong, I do like HP hardware,
just dont use any HP software with it (or ever for that matter).

We will probably never know why it screws up other apps.

The Frog