Juan,
IsRLocked() only works on the local machine. It returns wether you have an rlock() on a particular record, not if someone else does. This can be helpful if you are working in a slow network environment. The act of issuing RLock() will generate network traffic when you attempt to lock the record even if you already have a lock. You can avoid this overhead by checking to see if you have the record locked.
HTH.
>Hi,
>
>I haven't seen any problems when using RLOCK(), it really returns what Microsoft says.
>But I am not understanding ISRLOCKED() when opening a shared table in the server from 2 different machines:
>
>Machine 1
>
>use table1 && having only 1 record
>? rlock() && Returns .T. and status bar says: Record locked
>? ISRLOCKED() && Returns .T.
>
>
>
>Machine 2
>use table1 && status bar says: Record 1/1 Record UNlocked
>? rlock() && Returns .F. It's OK
>? ISRLOCKED() && Returns .F.
>
>
>Why ISRLOCKED() still returns .F. and status bar shows Record Unlocked message on Machine 2 ?
>
>
>
>Thanks.
>
>Juan.
Larry Miller
MCSD
LWMiller3@verizon.netAccumulate learning by study, understand what you learn by questioning. -- Mingjiao