Thomas Harmon asked:
 
>Is there any way to get around Images requirement of have the whole
>dataset locked when
>doing a DBPUT or DBDELETE? Our locking strategy is to only lock
>those particular entries
>that are capable of being changed which is easy with a MODE=6 and
>a lock list.
>Our problem is if any user has some entries locked for change mode,
>no other users can lock
>the whole dataset in order to do an add or delete.
>Surely there must be a solution other
>than not having entries locked during "think" time?
 
Sounds like a master, also I am assuming you don't want to
redesign any DB structure, so, one (not so elegant) solution is to:
 
 
(1) DBLOCK the DS
(2) DBPUT the record with the known master key
(3) DBUNLOCK
(4) DBLOCK the record only
(5) Do think time, enter remaining data on screen
(6) DBUPDATE
(7) DBUNLOCK
 
Not gonna work if you don't know the Key value (up front), or other
programs would burp if they read this incomplete record.
 
If you can change the master DS to a detail without much hassle, then
you would not have this (locking) problem.
 
Elbert