JETCOMP.EXE every day

[Rich Huhn]

When users attempt to open a database, they receive a
message stating that the database "needs to be repaired
or isn't a database file". We then get all users out of
the file and run JETCOMP and all is well... for a few
hours or a day... then it happens again. We have
experienced this problem occasionally in the past, but
since the database was moved to a new W2K3 server last
week, the problem now happens quite often. Coinsedense?
Any ideas would be greatly appreciated!

 

[Bruce M. Thompson]

When users attempt to open a database, they receive a

message stating that the database "needs to be repaired
or isn't a database file". We then get all users out of
the file and run JETCOMP and all is well... for a few
hours or a day... then it happens again. We have
experienced this problem occasionally in the past, but
since the database was moved to a new W2K3 server last
week, the problem now happens quite often. Coinsedense?
Any ideas would be greatly appreciated!

An excellent source of information on corruption (which is what you are
experiencing) is at Tony Toews' web site, specifically the following page:

Corrupt Microsoft Access MDBs FAQ
http://www.granite.ab.ca/access/corruptmdbs.htm

Other Access information can be found at his site at his Access page:

http://www.granite.ab.ca/accsmstr.htm