>Hi! I wonder if anyone can throw me his/her two cents. After a series of tests I still cannot reproduce the problem to be able to tell what is really causing it.
>
>I am testing in my local computer with only one instance of the form (a VFP 6 form) running and no copy of the file open anywhere else. Inside a transaction I rlock() the record very quickly and unlock it. I intermittently run into a problem where I cannot rlock() the record because it appears to be already locked. How could this be?
>
>I suspend the program once rlock() returns a .f. and check some settings: (1)the table has a table buffering of 3, (2)table is open only in the second datasession (I have two at the time), (3)I cannot unlock the table, which suggests that I was not the one who locked the record to begin with (but who/what could it be?) I did some wild tries like (1)I closed all the other tables/views and then tried to unlock the record again but to no avail. I have a non-updateable view open at the same time so I thought maybe that is being in the way. (2)I open a copy of the same table in another instance of VFP-- I could lock any record but the one that I was having trouble with. (3)I issue a use exclusive on the table and I am successful, proving that nobody else is really using the file but me.

If you are running AV software, try disabling any real-time scanning feature.