R
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!
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!