Protect File from Deletion

[Guest]

I have an Access database on a network drive and I am worried about someone
accidentally deleting it. Is there a way to protect the database from being
deleted?

 

[Rick Brandt]

I have an Access database on a network drive and I am worried about
someone accidentally deleting it. Is there a way to protect the
database from being deleted?

Users need fairly full permissions on the folder so the locking file (LDB) can
be properly managed. You can give them delete perms on the folder but not on
your MDB file but you will have to reset that every time you compact the file.

 

[Douglas J. Steele]

Users need fairly full permissions on the folder so the locking file (LDB)
can be properly managed. You can give them delete perms on the folder but
not on your MDB file but you will have to reset that every time you
compact the file.

The code MichKa has at http://www.trigeminal.com/codes.asp?ItemID=25#25
should help for resetting the permissions.

 

['69 Camaro]

Hi.

Is there a way to protect the database from being
deleted?

Those who need permissions to use the file will have enough permissions to
destroy it, too. If you think accidental deletion is a distinct
possibility, then hiding it from easy access should be considered. Please
see the following Web page for a link to the article, "Multiuser Databases":

http://www.Access.QBuilt.com/html/articles.html

Read option #4 and ignore the advice about using the /ro switch in the
Windows shortcut, because it doesn't apply to your situation.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[David W. Fenton]

Users need fairly full permissions on the folder so the locking
file (LDB) can be properly managed. You can give them delete
perms on the folder but not on your MDB file but you will have to
reset that every time you compact the file.

They don't actually need delete permission on the LDB file -- when
they log off, Access tries to delete it and it fails silently, with
no repercussions.

The only drawback of this (and I've done it in production apps) is
that if corruption develops in the LDB it stays around because it
never gets deleted. One way around this is to give certain users who
are trusted not to delete the file (your managers, maybe; or maybe
not!) by putting them in a user group that has delete permission on
the file. This means that any time one of those users is last one
out of the database, the LDB will be deleted. I've done that with
production apps and it works.

 

[David W. Fenton]

Those who need permissions to use the file will have enough
permissions to destroy it, too.

This is simply not true. You can set permissions on the folder to be
MODIFY but not DELETE, and it will still work.

If you think accidental deletion is a distinct
possibility, then hiding it from easy access should be considered.

That's not a very dependable method.

If you don't like running the risk of a corrupted LDB file, you can
set permissions on the file you're trying to protect, but keep in
mind that you have to reset permissions after a compact.