J
Jeff B
Recently the replicated Access 2000 application that I
have been designing for the company that I work for has
been behaving very badly, corrupting and giving
people "the databse needs to be repaired or isn't a
database file..." error and after all attempts at
compacting and repairing, recently entered data gets lost
because it does not tell those already in the db that
this problem has occurred, and they go on entering
information. Does anyone know what causes this, how to
deal with it, how to minimize the amount of times this
happens, etc? I have about 12 people using the replica
at the moment that currently resides on one person's
computer in a peer to peer network that will soon change
to a client server system. For the past 2.5 years, the
worst that happened was the "record is deleted" errors
that I easily solved but now it seems to have started
corrupting almost daily. Thank you for your help
have been designing for the company that I work for has
been behaving very badly, corrupting and giving
people "the databse needs to be repaired or isn't a
database file..." error and after all attempts at
compacting and repairing, recently entered data gets lost
because it does not tell those already in the db that
this problem has occurred, and they go on entering
information. Does anyone know what causes this, how to
deal with it, how to minimize the amount of times this
happens, etc? I have about 12 people using the replica
at the moment that currently resides on one person's
computer in a peer to peer network that will soon change
to a client server system. For the past 2.5 years, the
worst that happened was the "record is deleted" errors
that I easily solved but now it seems to have started
corrupting almost daily. Thank you for your help