Data Corruption

[Guest]

I have an Access database in 2003 that has a front end on the individuals pc
and the back end on a server. I have one user that has had the same problem
a couple of times. When editing data the record she is working on looses her
data and fields display ## or error or numbers that don't make since for
those fields. All other updates she had been working on were fine. It
doesn't appear that anything strange happened before this occurs or that she
did anything wrong. No one else is accessing this data when the error
occurs. She seems to be the only user having this issue.
Any help on why this would occur or how to keep it from happening again is
appreciated.

Cindy

 

[Guest]

After the errors appear on her computer, do the same records show up that way
on other computers? What happens to the records when she closes Access and
restarts it? If everyone can see the corrupted records and they don't go away
after rebooting Access, then the records are getting corrupted.

The problem is most likely with her computer. There's a very good chance
that there's a problem with the NIC (Network Interface Card), wiring, the
router/switch that it connects to, or the computer itself. Have your IT
department run a sniffer to see if there are any bad packets. If they don't
have that ability, just change out the wiring and NIC. Hopefully that will
fix the problem. If not it could be the computer.

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[Guest]

These are records in an audit and when she pulls up that audit the corrupt
record does not appear on anyones computer. I can go into the table itself
and see the corrupt record.

 

[Guest]

Most likely there's something wrong with her computer or the network
connection to it. It's possible that another computer not even using that
database could be putting out bad packets and causing a problem. A sniffer
could find this.

Does she have any other problems with that computer? If so, that's the
really points to the source of the trouble. I would not let her use the
database until the problem is fixed or the database might become completely
corrupted. I recommend frequent backups including one right about now.