Windows 2000 Server and Access 2000 constant corruption

[Mark]

The company I work for has been running Access 2000 on a Windows NT
server with Opportunistic Locking turned off on the server without
issue for almost a year. We have just switched to a Windows 2000 file
server with service pack 3 installed and are now experiencing at least
2 corruption's a day. The registry setting for Opportunistic Locking
that was on the Windows NT server does not exist on the Windows 2000
server so we can not make the needed change to the new server. From
what I understand service pack 3 is supposed to take care of this
problem. Does anyone have any suggestions on how to proceed? Any help
would be appreciated as this has caused a very unstable work
environment.
Regards,
Mark C.

[Larry Linson]

While I am not an infrastructure person, I am almost certain that you can,
indeed, turn of OpLocks in W2000 Server -- but it wouldn't surprise me that
it is in a different place in the menu structure.

The best collection of links and information on the subject is at MVP Tony
Toews' site, http://www.granite.ab.ca/accsmstr.htm. If the details of
turning off OpLocks aren't there, it's very likely there's a hyperlink to
another source where you can find the details.

Larry Linson
Microsoft Access MVP

"Mark" <he******@yahoo.com> wrote in message
news:cb********************@comcast.com...

The company I work for has been running Access 2000 on a Windows NT
server with Opportunistic Locking turned off on the server without
issue for almost a year. We have just switched to a Windows 2000 file
server with service pack 3 installed and are now experiencing at least
2 corruption's a day. The registry setting for Opportunistic Locking
that was on the Windows NT server does not exist on the Windows 2000
server so we can not make the needed change to the new server. From
what I understand service pack 3 is supposed to take care of this
problem. Does anyone have any suggestions on how to proceed? Any help
would be appreciated as this has caused a very unstable work
environment.
Regards,
Mark C.