Corruption problem

[mike]

I have an access 2002 database that's functioned fine for years but now keeps
becoming corrupted somehow. The problem occurs in one table in particular --
a record will be inserted or altered so that the primary key is null and all
the other fields display as ######. In addition, somehow the primary key
keeps getting "unset" -- the field is no longer designated as the key. This
has happened a dozen or so times so far. I've never heard of any problems
where the table properties get altered through the general use of the
database before.

I've recreated the table a number of times. I've also recreated the entire
database from scratch and the problem keeps recurring. I built this database
for a client years ago, and the problems started cropping up only recently
when they had some new people start. Has anyone encountered anything similar
to this before? I'm completely stumped as to what's occuring.

Is there any possibility that different users logging in under the same user
id could cause this type of problem? The database itself doesn't require a
login, but two people are using the same network login (don't ask me why -- I
don't do any of their networking, just this database)

 

[Jerry Whittle]

I'm betting that one of the new users is messing with the database! Is the
database split? It should be. Password protect the back end and relink the
front end. Give the password to only one or two trusted managers. Between the
splitting of the database and keeping users out of the design, I bet the
problem goes away. If not, here's some other resources:

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