Re: Database Corruption

I didn't split the database by "front-end" (forms) and "back end" (data).
You've already got people telling you this is the cause of corruption. Me
too.

This captures all users' activities including "abnormal exits" ...
OK, I'm Curious. How exactly do you capture "Abnormal exits"? The only way
I've found to identify them is by what did *not* get captured. I have a log
much like you describe but I can only identify abnormal exits by locating
Logins that don't have a corresponding Logout (i.e., the user had to have
used Task Manager or Power button to exit).

--
HTH,
George


"Fred" <Fred@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:10359C99-57B4-4DFC-B10F-5D291191C198@xxxxxxxxxxxxxxxx
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?



.

Loading