This always depends on the access level that the user has. Generally speaking Data Entry people are unable to do things like this but people higher up the food chain are.
If you have someone in the position of Junior Manager or the like about all you can do is perform incremental backups on a very regular basis and maybe even mirror the data on the file server to another severs which the user can not access. That way when a new file is added or an existing file altered it will be copied to the backup server but it can not be deleted by a disgruntled worker who is leaving one way or another.
I've also seen [b]Time Bombs[/b] left on a system so a long while after a worker leaves the bomb goes off totally erasing everything on any switched on computer generally these are set to run at lunch time on a Friday afternoon when people are not really paying much attention.
The only real way to prevent loosing all the files is to keep doing a [b]Real Time Backup[/b] but even this is no guarantee that things will not be done to the system by someone sufficiently Peeved Off and with most of these incidents companies rely on their backup to recover. At one place that I went into after the System Admin had been disposed of under less than ideal circumstances I had to hack every computer for BIOS passwords and it only got worse from that point on. I particularly liked the idea where all the data was encrypted on the file server but the encryption keys where stored locally on the workstations it made life so much fun to repair that network.