Access Reports Running toooo slow

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi
We have access 97 application split into Client ( residing on local m/c ) and Backend (on server). The reports are running too slow than the mirror copy which isnt used frequently. We tried compacting the database both frontend and backend but doesnt help.
 
Do your underlying queries also run slowly? Are your tables indexed? What
speed is your network? Can your network folks "sniff" the connection for
re-sends? Do you have a network antivirus -- this can cause a major
slowdown in performance for all Access operations?
 
S. Ahuja said:
Yes underlying queries are also too slow...tables are indexed..100Mbps.antivirus : yes.
I tried by copying the backend to the local m/c still the performance is tooooo bad ( report takes 10 min to run ) on P IV
with backend and frontend on single m/c.
Click to expand...

I'd suspect the antivirus software. Or a recent update. Another
update might fix the performance problem.

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
 
The mirror copy of the database is somewhat faster(though not tooo fast)...dont know why ? The data in the backend is also not too much that performance is hit.
 
At one of the Access installations I support, the applications suffered a
sudden, severe slowdown in performance. As it turned out, this was
immediately following an "upgrade" to the antivirus software.

The short-term solution was to have the Antivirus Admin add the Access
applications to an "exclusion" list. This returned the apps to their
previous performance.

The long-term solution was to have the Antivirus Manufacturer patch their
faulty update.

This was my experience, in my situation... your situation may not be the
same. I re-iterate my suggestion that you have the network gurus "sniff"
the transactions to see what they can spot. This was how the antivirus
issue was identified in my situation.
 
Back
Top