We do not allow all of our users full access to the fileserver, for reasons which should be obvious. There are many things in the Recorder6 folder which should not be fiddled with and the simplest way to control this seems to be to restrict access for our volunteer users.

Today I have noticed a couple of problems which stem from this.

A user is entering data via a recording card, there are some species he needs to enter which are missing from the card, so he adds them, enters the data and saves it successfully. Then when he closes the card he is asked if he wants to save changes to the card, he clicks yes, but doesn't have modify permission and this causes an unhandled exception (access violation).

Obviously this is partially our fault for denying him access, but we don't want him modfying recording cards (or other files stored close by & used by all of us). But the fact that the exception is not handled more gracefully is not our fault. Could the exception not be trapped, telling him he doesn't have sufficient rights to overwrite the card, but asking if he would like to save it under another name (we don't mind giving him write permission instead of modify). Our volunteers get justifably jittery when they see the Unhandled exception message.

The second, related point, is that as far as I can tell this unhandled exception is unable to generate LastError.txt because we have not given him write access to the root recorder 6 folder. That means that if I am out of the office when an error occurs with one of the volunteers, I get back to be told there was an error, but I can't find out the details. We have fixed this by granting write, but not modify access to the root folder.

This brings me to another point. Is it possible to change the default location in which LastError.txt is created. We have a range of different errors occurring sporadically on various workstations, but each one overwrites the file generated by the previous one. I would prefer that the report file was saved locally on each workstation.