RLock Function (Usual)

Request Example View Source

Parameters

uArea

Type: Usual
Specifies the work area name or number for a table on which the operation must be performed.

Return Value

Type: Logic
TRUE if the record lock(s) is (are) obtained; otherwise, FALSE.
If you try to lock more than one record and one of them fails then locks that were successful are released again.
An attempt to lock a record in an empty database returns TRUE.

If a database file is opened in shared mode, you must obtain a record lock before attempting any operation that writes to the database file. For each invocation of RLock(), there is one attempt to lock the target record, and the result is returned as a logical value.
An attempt to obtain a record lock fails if another process currently has a file lock or record lock on the target record. If RLock() is successful, the record is locked and other processes are prevented from updating the record until the lock is released. RLock() provides a shared lock, allowing other users read-only access to the locked record while allowing only the current process to modify it. A record lock remains in effect until you explicitly unlock it (with DBUnLock(), for example), close the database file, or attempt another file or record lock (with RLock() or DBRLock() without an argument).
By default, this function operates on the currently selected work area.
It can be made to operate on an unselected work area by specifying it within an aliased expression or by calling the overload that accepts a workarea parameter (a workarea number or alias ).
This feature is useful since RLock() does not automatically attempt a record lock for related files.

This example deletes a record in a shared database file using RLock():