>>Procedure cancelled can come from a trigger (RI, you're correct). We had these errors. You may want to dive deeper into the trigger's code.
>
>Well, the 1099 error was caused by some test code I left in there. Doh! So now what I'm getting is a 109 error (Record is in use by another user). Well, this is a record that was added by the program and not one that any other user should be accessing. The table in question is an inventory transaction table, so there's never any editing of a record. It's all about adding records when it comes to that table, because it's just a record representing the removal (in this case) of a certain number of items from the inventory (which is represented in another table). So the inventory record has the qty available reduced by X and a record is placed into the inventory transaction table representing the fact that so-and-so user decremented the inventory for the item by X. The update fails on the inventory transaction table with the 109 error. Since any user performing an action that decrements inventory will create their own unique inventory transaction table record related to that decrement, no user should ever be interfering with another user's record. Possibly the record pointer in the inventory transaction table might be sitting on that record, but it would not be locked. Any thoughts on what might be causing this?

I know we were getting these errors quite often as well, but I don't remember right now if we were able to resolve the cause. I'll send a link to this thread to my former colleagues if they have more info for this problem.