Database Corruption

I have a multi-user application that executes on a runtime on a file server.
I didn’t split the database by “front-end” (forms) and “back end” (data).
When there is no corruption, the database runs smoothly for days. On
occasions, the database gets corrupted thereby needing a manual “compact and
repair” process.


The Error Message is:
"The database “\\Land\Copy (3) of Property.mdb“ needs to be repaired or
isn’t a database file. You or another user may have unexpectedly quit
Microsoft Office Access while a Microsoft Office Access database was open. Do
you want Microsoft Office Access to attempt to repair the database?"


I created a program, within the database, to monitor users’ login and
logout. This captures all users’ activities including “abnormal exits” (date
and time). There doesn’t seem to be any pattern of users exiting abnormally
that would cause the corruptions. The database (“mdb”) gets corrupted even
when there are no abnormal user exits.

What could possibly cause the corruption?

.

Relevant Pages

  • Re: Attempt to fetch logical page
    ... You have a corruption in your database. ... Second, if you are on SQL Server 2000, check the specific recommendations for your error. ... This error occurs when Microsoft® SQL ServerT detects database corruption. ... execute DBCC CHECKDB to determine the extent of the damage. ...
    (microsoft.public.sqlserver.server)
  • Re: Do Transactions guard against corruption?
    ... when the database is opened and closed. ... meant by 'corruption'. ... Transactions have NEVER been designed as safeguard for those previous ... not used by Access to protect the structure of the database. ...
    (microsoft.public.access.modulesdaovba)
  • Resolution: TurboIMAGE database being corrupted by QTP
    ... data set in question would eventually result in an error, ... database in a corrupted state. ... supposedly have at least one LFDS. ... very next DBPUT triggered the error and the corruption. ...
    (comp.sys.hp.mpe)
  • Re: database corruption
    ... Corruption is a possibility, but what's more ... the system warnings need to be turned back on in the error handler ... Either adding appropriate error handling or not ... by preventing the database from even opening. ...
    (microsoft.public.access.setupconfig)
  • Re: Database Corruption
    ... You've already got people telling you this is the cause of corruption. ... How exactly do you capture "Abnormal exits"? ... the database runs smoothly for days. ... Microsoft Office Access while a Microsoft Office Access database was open. ...
    (microsoft.public.access.formscoding)