pd******@steelcase.com (Pamela DeVries) wrote in
<3f*********************@news.frii.net>:
There is a constant battle right now between
my department (Access Development Services) and the network team.
They insist nothing is wrong with the network.
For what it's worth, in all my years of Access work, I've never
seen corruption caused by bad network hardware. Others have
different experiences, but mine go back to 1996 or so and with a
variety of clients.
I am excluding user error, of course (e.g., pulling the power plug
while a database is in use), and obvious things like unstable
workstations that are hosting the data file and crash while other
users are editing the data on the machine that crashed.
In A97, the only corruption I ever saw at all was in a replicated
back end and was caused by the application on the server where the
replicated data file resided of a Microsoft Exchange hotfix. The
corruption first happened within 2 hours of the application of the
hotfix and stopped as soon as we figured it out and backed out the
hotfix (it wasn't needed in the first place as Exchange was not in
use!).
In A2K, I've seen a lot more incidents of corruptions, all of which
were software issues for the version of A2K and the Jet db engine.
Once A2K was at SR1+ and Jet at SP6 on *all* workstations, the
problems went away *permanently*. I have been through this with at
least 4 clients that I can think of off the top of my head.
So, if it's A2K, before I went back to the hardware guys, I'd make
sure that 100% of the workstations are at SR1 or higher and have
Jet SP6 or higher. And it takes only *one* workstation out of 50 --
been there, done that.
--
David W. Fenton
http://www.bway.net/~dfenton
dfenton at bway dot net
http://www.bway.net/~dfassoc