Is your EDIT button issuing an RLOCK() on the current record? If so, when you leave that record it will remain locked because SET MULTILOCKS must be on for buffering. You need to issue and UNLOCK before you leave that record -- perhaps in a SAVE button or in your Prev/Next buttons?

If you modify the code in the EDIT button to remove any explicit locking, VFP will automatically issue a lock on the record when editing begins, and unlock the record when you move to another record.

>I discovered that when I am running my multi-user form in buffering mode 2 and press my Edit button I am allowed to edit my record at the end of the table, but when I press Prev and then edit to edit the previous record in the table, I get an error 109 which means the record is locked by another user. But I am running in standalone mode. So I hit Prev button again and hit Edit again and got the same error. I kept doing this for several times until I was about 10 records prior to where I started, then I was able to Edit the records without error 109.
>
>I tried the command window and did UNLOCK ALL thinking that would unlock those locked records. How can some records be locked and some unlocked in single user form running mode. It almost seems as though VFP locked those records permanently the other day when I was testing with 2 users at the same time. And I can't unlock them. Any idea what's going on with this? If I can unlock those records or figure out how come they appear to be permanently locked, I will be home free.
>
>Thanks again.