Difference between revisions of "SET LOCKWAIT"
Yvonnemilne (Talk | contribs) |
Yvonnemilne (Talk | contribs) |
||
| Line 13: | Line 13: | ||
==See Also== | ==See Also== | ||
| − | [[ | + | [[FLOCK()]], [[LOCK()]], [[LOCKF]], [[LOCKR]], [[RLOCK()]], [[UNLOCK]] |
Revision as of 11:06, 2 June 2009
Class
Environment
Purpose
Enable or disable automatic record locking
Syntax
SET LOCK ON | OFF | (<expL>)
SET LOCKWAIT ON | OFF | (<expL>)
See Also
FLOCK(), LOCK(), LOCKF, LOCKR, RLOCK(), UNLOCK
Description
The SET LOCKWAIT command determines locking behavior when you attempt to gain UPDATE access to a record which is already locked by another user. This command is only effective with shared tables. With SET LOCKWAIT ON, commands such as REPLACE will wait until a lock can be obtained. With SET LOCKWAIT OFF, an error will be generated, telling you that the operation cannot take place as the ’Record is in use by another user’. In the forms system, both settings give you the opportunity to either wait for the record to be unlocked by the other user and your lock to be granted, or, to access the record in QUERY mode. To switch from ’Query’ mode to ’Update’ mode in a form, press the [UPDATE MODE] key. By default, LOCKWAIT is ON.
Example
use patrons index events, dates, names set filter to event = "HAMLET" browse
Products
Recital Database Server, Recital Mirage Server, Recital Terminal Developer
