T
Teoman Haliloglu
We have been using an application developed with Access 97
on Windows NT server.
Recently we've been making some tests to switch to windows
2000 server, and saw that our Access uses processor at a
very high rate (closer to 100%, even at idle times, even
with a blank database and form with no data), a problem we
didn't have with NT....
Processor use goes up even single mouse move or click and
stays there for a while.
Since we are using Terminal Server and will be using
Terminal Services when we switch to win2k, this problem
gets more serious. (I can't think of 40-50 Access sessions
eating processor at those rates on a poor Terminal
Server!!!)
Any ideas? Thanks in advance...
Teoman
on Windows NT server.
Recently we've been making some tests to switch to windows
2000 server, and saw that our Access uses processor at a
very high rate (closer to 100%, even at idle times, even
with a blank database and form with no data), a problem we
didn't have with NT....
Processor use goes up even single mouse move or click and
stays there for a while.
Since we are using Terminal Server and will be using
Terminal Services when we switch to win2k, this problem
gets more serious. (I can't think of 40-50 Access sessions
eating processor at those rates on a poor Terminal
Server!!!)
Any ideas? Thanks in advance...
Teoman