Hello,
Our application developer has recently rewritten one of our database apps from scratch using Access 2003. The application is split, with the back-end sitting on a server and the front-end on PCs, picking up back-end data through linked tables. A second front end with a different function also picks up the back-end data via terminal services in the same way.
The problem is that after a few days of reasonable performance, the front end app slows down dramatically in a short space of time, even though front and back end databases aren't very large (<20MBytes). The "old" system has databases ten times that size and worked without complaint. The only way to restore performance is to compact and repair the databases.
We've tried all the usual tricks such as killing off subdatasheets and reconfiguring anti-virus sweeps but nothing seems to have an effect.
Has anyone experienced this type of behavior before? Did you manage to find a solution?
Our application developer has recently rewritten one of our database apps from scratch using Access 2003. The application is split, with the back-end sitting on a server and the front-end on PCs, picking up back-end data through linked tables. A second front end with a different function also picks up the back-end data via terminal services in the same way.
The problem is that after a few days of reasonable performance, the front end app slows down dramatically in a short space of time, even though front and back end databases aren't very large (<20MBytes). The "old" system has databases ten times that size and worked without complaint. The only way to restore performance is to compact and repair the databases.
We've tried all the usual tricks such as killing off subdatasheets and reconfiguring anti-virus sweeps but nothing seems to have an effect.
Has anyone experienced this type of behavior before? Did you manage to find a solution?
