Michasam said:
I work in a department where we all access an issues database in
Access that is located on a server. I get very quick response time
but a co-worker is getting extremely poor response time, even just
opening the database up. Our machines are set up very similarly and,
in fact, his is faster than mine. None of the other Office
applications seem to be affected this way and he is the only one who
appears to have this particular problem.
Any clues on how we could resolve his performance issues?
Does the slowdown affect (a) just this one database, but not other
databases on the same server, (b) all databases on that server, but not
other servers on the network, (c) all databases stored on the network,
but not databases stored on the local PC, or (d) all Access databases?
There a couple of possible culprits here. The first one that comes to
mind is the operation of antivirus software. Many AV products, by
default, will scan any .mdb file you open over the network, before
allowing it to open. If this is the problem, your co-worker should
check the option settings for the antivirus software and tell it not to
scan .mdb files.
Another possibility is that your two workstations have a different
network path to the server, and that somewhere along your co-worker's
path, there's a slow link. If he doesn't perceive any slowness
accessing any other files on that server, though, that's probably not
the problem.
Another thing to check is that there might be something in your
co-worker's Access settings or installation. Does the slowdown affect
..mdb files stored on his workstation, or just the one on the server?
Are you both running from a locally installed copy of Access, not from
an application server? Does he have the Name AutoCorrect option turned
on, while you do not?
Is this a "monolithic" database, where all the users are directly
opening the same database on the server? Or is the database split into
a front-end and back-end database files, where the back-end database is
stored on the server, and each user has his own copy of the front-end,
which has its tables linked to the back-end? This latter arrangement is
best for a networked Access application, though the matter probably
doesn't have any direct relevance to your immediate problem.
