Access not responding

[Guest]

Help,

I have an Access db split in to front end (10 mbytes) and backend
(30Mbytes). When the backend is local, on my C: drive, the system is really
fast. On the network, however, the database response is in excess of 60
seconds, even for a single record retrieval.

I compact & repair both db's regularly (2-3 times a week).
This is the case when I am the only user or when 3 concurrent users are on.
When I copy the database to the network drive it normally takes only 10
seconds.
The biggest table is only 15,000 rows.
Windows Task Manager reports access as 'Not responding'.

Can anyone help on this.

Many thanks in advance,
APS

 

[Jeff Boyce]

One possibility (speaking from painful personal experience) is that the
network has received an "upgrade" to an antivirus program. Following such
an upgrade, my front-end/back-end apps all suffered horrible response time
(1 minute and more).

See Tony's site for more ideas on slow performance...

http://www.granite.ab.ca/

Regards

Jeff Boyce
<Office/Access MVP>

 

[Guest]

Please excuse me for using reply for this. I am trying to post a question
about Access. I'm at the page where I'm supposed to select from a list of
questions previously posted. No matter what I do, I cannot find any way to
post my own question. Can anyone please help me? I'm at (e-mail address removed)..

 

[Guest]

Hi Jeff,

Thanks for the response, IT say they are applying upgrades all the time.
Could this result in a 60 second response on selecting an option within the
app, yet only a 10 second response on the file copy?

 

[Tony Toews]

I have an Access db split in to front end (10 mbytes) and backend
(30Mbytes). When the backend is local, on my C: drive, the system is really
fast. On the network, however, the database response is in excess of 60
seconds, even for a single record retrieval.

I compact & repair both db's regularly (2-3 times a week).
This is the case when I am the only user or when 3 concurrent users are on.
When I copy the database to the network drive it normally takes only 10
seconds.

Once a client had very poor performance which compacting didn't
correct. However importing the tables and relationships into a new
MDB did fix the performance problem.

Did this performance drop happen suddenly, has it always been like
that or has it been slowing down over time.

Now the bulk of the suggestions at the Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm deal with multi
user issues and don't appear with only one user. However some will
still make a difference with only one user. All of them would be
relevant in any case.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Jeff Boyce]

In my situation, the queries ran out to three minutes or more...

Jeff Boyce
<Office/Access MVP>

 

[Guest]

The response has always been poor. the users are just complaining more now. I
tried moving the db to the root of the network drive and shortening the name
to 8.3 format as recommended in the site you mentioned. This seems to have a
small, but noticable difference.

 

[Tony Toews]

The response has always been poor. the users are just complaining more now. I
tried moving the db to the root of the network drive and shortening the name
to 8.3 format as recommended in the site you mentioned. This seems to have a
small, but noticable difference.

Well, try the other things mentioned on that page as well. Even if
you are only testing on one user once you go to multi user they will
make a difference then.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm