Wayne Aprato wrote:
Is there an effective method of preventing users from accidentally or
maliciously deleting the database file/files from a shared network
drive? At the moment, I'm using a batch file to copy the data.mdb to
another secure location every time a particular user who performs most
of the data entry exits the database. Setting the windows permissions
for the database folder to "read only" seems to create problems and
data entry users obviously can't enter data.
Any help would be appreciated.
I think you have an HR problem rather than an IT problem.
IMHO there is a shortfall in Windows' file permissions, especially for
networked drives. In Novell you could explicitly allow read and write
but prohibit delete. In Unix you'd give them a link, reading/writing to
that link would read/write to the base file but deleting the link would
only delete the link and not the file.
Off the top of my head (which feels very thick and groggy today) I can't
think of anything do with poermissions on a Windows server so my only
suggestion would be to link the tables to a hidden share (share name
with a $ on the end), not that secure but safe from the casual browser.
A bit like Isla de Muerta, cannot be found except by those who know
where it is (damn, I changed from my Rum sig, so appropiate in this
case<g>).
--
Error reading sig - A)bort R)etry I)nfluence with large hammer
