Corrupt Database

[tom.forestall]

Our Access 2000 databases are constantly being corrupted
by impatient users that exit using the AL_CNTRL_DELETE
function.
MSAccess 2000 flags a database as being corrupt any time a
transaction can not be completed (even a select query)
New users can not access the system because the database
appears to be corrupted. The database can not be repaired
until all users are out of the system.
Is there any way to prevent this database corruption or a
quick way to force all users off the system so that the
database can be repaired.

 

[John Vinson]

Our Access 2000 databases are constantly being corrupted
by impatient users that exit using the AL_CNTRL_DELETE
function.

Yep. That's a very good way to corrupt a database.

User education is probably your first line of defense here: explain to
users that this is very much like shutting off the ignition of your
car at full speed on the <busy area freeway of your choice>, and that
they simply SHOULD NOT DO THIS, EVER.

There are some tools at http://www.mvps.org/access to identify (and I
believe evict) users... but there's no way to prevent the corruption
if users do this.

 

[Kevin3NF]

Charge 'em $50 for your time, each time they do it.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[GVaught]

Is your database split into a Back-end and Front-end scenario? Back-end on
Server and Front-end on each users machine? If not, it should be. Keeping
the database as one mdb file is the leading cause of corruption from
multiple users. Although, a user can still manage to corrupt the database
with this setup it is minimal.

John's analogy is quite good and I agree user training is a must. If the
database is already corrupted, then code within the database wouldn't do any
good for 'kicking' users off because you can't open the connection. You may
be able to create a secondary database that will record who is logged in and
use that database to kick user's off, however I am not sure how you would do
this. Perhaps a MVP would have some code or idea.

I would charge the culprit(s) $100 per incident and $1000 dollars if the
database becomes unrepairable. Docking there pay may get them to realize
this is serious.