I **think** your test may be flawed.

If you're doing the second session on the SAME workstation then I believe you can lock the same record over and over again.

good luck

>It recently came to my attention that in our application record locking is not working.
>As a test I open a command window and open a specific record. Open a second window and at the same point in code (susp) issue an rlock(). It should not be .t. since the record should be locked. Similar tests on flock() do work.
>
>I'm not sure if this is a Foxpro problem, or a Novell problem. I'm going to run a packet scan this weekend.
>
>I'm also concerned that implicit locking may not be working.
>
>If any body has dealt with a similar issue or has any thoughts they would be most appreciated.
>
>Any suggestions on better or more conclusive testing would also be appreciated.