>Check to see if reprocess is set to zero. If so when one user attempts to lock a record that another user is currently editing (even with a browse window open) that scrolling "attempting to lock message comes up and will stay up until the other user exits that record.

As far as I know, the reprocess setting is left default (e.g. 0). My colleague and I both tried to convince our other colleague, who is in charge of classes changes, what this setting is very important and should not be left unchanged. We both failed in this...

Anyway, this particular problem seems to be a Network problem and not related to this setting...

We're using Novell Network at work. I also raised another similar issue in another thread. Sometimes without any apparent reason the user sees a message: "Record or file is not available." (something like this). I'm positive, that there are no other users, which open this particular file at this moment...

I'm not sure, what should I do at this point as a programmer...