back-end corrupted file

[Guest]

Users (18) have Access XP, network uses Windows NT 4.0, bk-end located in
network server.
Our system had been working without any problem for over three years. Back
-end Data got corrupted only once in those 3 years. However in the last 3
weeks back-end data got corrupted twice already. The first time I didn't
worry too much because it hadn't happened for over a year. The second time it
happened (yesterday) I did worry. The message that everyone was getting was
"Invalid argument" and then their front-end froze.
I asked everybody to log-off. I was going to open the back-end in exclusive
mode but I couldn't because a user who went to lunch didn't log-off. He
actually was working from his front-end! I went to another machine log-on and
was able to access the back-end data w/o any problem. Everyone was able to
access the data, except one user.
I am asking the IT guy to check her machine for any possible weak signal
(her computer is wired rather than wireless) he says strenght has nothing to
do with it, he blames the Access front-ends.
I am flabbergasted... any suggestions? I have daily back-ups but restoring
the backup data is time consuming and there is always data that users have to
retype.

 

[Arvin Meyer [MVP]]

1. If all users work except 1 front-end, it's that front-end that's corrupt.

2. Anyone still running NT4 after all these years of security problems has
no room to talk about Access or anything else.

3. NEVER run Access on a wireless connection. They are undependable. Dropped
packets can corrupt databases.

4. Flakey networks will corrupt any large file, not just Access. You IT guy
needs to check that machine, the NIC, and the cabling.