Thanks, Cetin. -- Well, Set Excl is off. I'm not sure about Multilocks but I will check. I did, however, simplify the situation in the following manner and users received the same error: I put the routine (it's to close out accounting stuff for the month) into a separate data-utilities program that doesn't open any files in any other datasession. The data-utilities program will not run if anyone is in the system from any machine, and none of the programs will run if the Data Utilities is up. (I don't touch the data to accomplish this. Instead I use a low-level file locking strategy with a dummy file.) So, basically, there can only be one user and one datasession. The files, furthermore, are opened only once in the routine. But the error still occurs.

But it only happens if the data is on the network. If we get the user to copy the data to their hard drive, then run the routine and copy the data back up, it works. I do not know whether the problem has occured on non-Novell networks.

Adam