By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,098 Members | 1,950 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,098 IT Pros & Developers. It's quick & easy.

Recurring data file corruption leading to my insanity

P: n/a
Please forgive me, this is a long one.

My 11-user Access 2000 database is having recurring corruption
problems. The symptoms include the following:

1) corrupted fields in recently created or accessed records
2) incorrectly linked records via primary and foreign keys (looking at
the tables displays the correct key number but when filtered it links
to a different number).
3) truncating of text entered in a memo field
I am able to repair the data file every time. But, to be thorough, I
have gone so far as to re-create the table definitions by hand in a new
database and import the repaired data by way of comma delimited text
files. At this point, I also created a new, albeit simplified,
front-end to be sure that was not the issue.

Nevertheless, corruption still occurs. I have re-linked each individual
user to their own copy of the data file (stored on the same server as
the group data file) and was unable to re-create the corruption
problems. But when more than one user links to the same data file the
corruption takes hours, if not minutes, to occur.

I have scanned each computer for viruses. I have uninstalled and
re-installed the runtime and front-end on each machine. I have recently
compared various files' versions. There were discrepancies but these
were attributed to the fact that some users were running XP while
others were still on 2000. One discrepancy was the Jet engine file but
there were several users on XP long before data corruption began to
occur. The same goes for MDAC, DAO and comctl32.dll files.

The tech department is reluctant to assist me in analyzing our
hardware, though we are located in a different building than the server
and the network equipment and cables are fairly antiquated.

The only change I can identify that occured around the same time as the
beginning of these issues is that the server that the data file was on
was upgraded. At the time, the data file was still in use and, having
"touched" every file on the server during upgrade, this is likely what
initially corrupted the data file.

So, is there anything I am missing here? Does anyone have a clue as to
what would cause recurring corruption after a brand new, clean data
file was created? I am pounding my head against the wall and no longer
sleeping well! A pre-response thank you goes out to anyone that can
help me.

May 3 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
>Does anyone have a clue as to what would cause recurring corruption

Check out:

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

May 3 '06 #2

P: n/a
Thanks. I've already managed to come across that one in my research
though. Along with various other support websites and Microsoft's
Knowledge Base, nothing seems to describe my situation. I can repair
things just fine and have taken all of the steps outlined to ensure
that the data file is actually repaired and suggestions on preventing a
future corruption, but it is all to no avail.

My main stumbling block is that virtually nothing has changed between
the last five years of use and the recent two months of continued
corruption. Other than the fact that a server upgrade coincided with
the original corruption of the data file. Also of note, our
organization is running on Novell.

May 3 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.