Hi Mark,

I am not doing any explicit record locking. I never used RLOCK(). I do have SET MULTILOCKS ON for buffering in my Form Init and start the form with GO BOTTOM in the Form Init. I press the Edit button and edit the last record in my table, no problem. Then, I hit Prev button and go to the previous record and press the Edit button and get the 109 error. And then I repeat those same button presses (Prev followed by Edit) for about 7, 8 or 9 times until I finally reach a record that lets me into edit it.

In my edit mode I do use REPLACE and have some ControlSources set to that same table in my textboxes and comboboxes, but that's about it.

I am getting the 109 error with no other users running at the same time. It seems to think I went in to edit those records and came back out without unlocking them and then tried to go back in and edit them again. But I have never edited those records before even though it thinks I have. Because why else would it be thinking that the records are already in use.

There must be something different about those records, but they are all in the same table with 4000 other records and it appears I can edit most all of the 4000 records except for a few that claim to be locked.

I might have gone into those records over the weekend in my multi-user testing and caused some locks to occur to those records during that testing, but why would they still be locked. Is there a way to manually go into the offending records and UNLOCK them. I tried USE mytable and UNLOCK ALL in the command window, but no help.

I am trapping the 109 error in my Edit button with AERROR command and returning a message to the user that "This record is already in use at another workstation. Please try editing this record again later." That sort of thing.