Access 97 Performance on Windows 2000 Server

[JonDotCom]

A server that was running NT 4.0 with Access 97 was just upgraded to
Windows 2000. Now Access jobs are taking 2 to 3 times as long to
complete. Found in one forum that Access 97 and Windows 2000 are not
completely compatible, but could not find any information on this
anywhere else. Anyone have any information on this?

 

[Albert D. Kallal]

I have run a97 on win2000 boxes and also on win XP boxes. The results were
fabulous, and the rock solid.

The only real know problem is that some registry security issues can come up
if users and ms-access are not run with admin privileges.

As for performance issues? I found win2000 to be better then previous
versions when running it with a97. It really works good.

However, I have MANY times seen that if the a97 application does NOT keep a
persistent connection open to the back end, then, things REALLY slow down.

The above simply means that when the a97 application starts, you need to
open a table to the back end (any table is fine!). You can even manually
open a table, and then just min it. Now run the rest of your application.
You will find the performance returns. (thus, just keep a table opend to the
back end).

The following is a check list for a2000. The one thing that applies to you
is the persistent connection. Give that trick a try. A quick read will also
suggest to check things like virus software, and if the path name to the
share is too long.

 

[Albert D. Kallal]

Opps, that check list:

http://www.granite.ab.ca/access/performancefaq.htm


Just remember, if the "min" a open table trick does NO help you, then you
don't have the "persistent" connection problem..

 

[JonDotCom]

This is Overnight Processing that is located on a Windows 2000 server,
the problem that we are having is in the nightly update for this Data
Warehouse. There is no problems with the front end connections, this is
a server problem.