J
JohnMc
I recently installed the latest MS Office 2000 sp3 on a clients network.
These 10 workstations were running fine with the original install of
Office2000 until the upgrade was performed. Since sp3, some users are
complaining of slow response and performance problems. One user has the
habit of using ctrl-alt-del to exit the access FE software I created.
Reason: system hangs or is too slow to respond.
Does anyone know of problems with Office 2000 sp3 that could cause such
degradation in server performance? The identical software BEFORE the update
ran well but now can easily hang if 2 users access the same data or if a
random record is saved.
If it was db design, I would have expected this problem years ago as these
FE applications have been running for 4 years. Database is regularly
compacted. In an effort to solve this problem, I've used both Access db
compact utility and the jetcomp.exe program. I have no trouble with the
*.ldb file expect when the above user closes his system incorrectly.
Recent analysis of the forms and database reveal nothing except a suggestion
to index a minor field "stateAbbrv". I can't see why this small data field
could cause such degradation in performance.
Any comments or suggestions?
These 10 workstations were running fine with the original install of
Office2000 until the upgrade was performed. Since sp3, some users are
complaining of slow response and performance problems. One user has the
habit of using ctrl-alt-del to exit the access FE software I created.
Reason: system hangs or is too slow to respond.
Does anyone know of problems with Office 2000 sp3 that could cause such
degradation in server performance? The identical software BEFORE the update
ran well but now can easily hang if 2 users access the same data or if a
random record is saved.
If it was db design, I would have expected this problem years ago as these
FE applications have been running for 4 years. Database is regularly
compacted. In an effort to solve this problem, I've used both Access db
compact utility and the jetcomp.exe program. I have no trouble with the
*.ldb file expect when the above user closes his system incorrectly.
Recent analysis of the forms and database reveal nothing except a suggestion
to index a minor field "stateAbbrv". I can't see why this small data field
could cause such degradation in performance.
Any comments or suggestions?