>Just a long shot.......
>In an app I inherited, which doesn't use buffering either, the clerk gets an occasional update conflict message because she/he bangs to "Save" key too hard and causes a key bounce. Trapping the key strokes immediately before the save code is executed seems to have cured the problem.

Here, there is no save button as no buffering is in effect. However, they get the error when pressing the delete button. They do that with the mouse. I don't think they would have clicked too fast for all those tests. :) Also, the programmer there did some tests as well. As soon as they press delete, they have the error.

I will check the error log of the client to see if I can find more clues.