RList unlocks records - feature? (AREV Specific)
At 28 NOV 1998 11:00:25AM Paul Simonsen wrote:
Howdy,
I just finished a report which locks several records within a file (because these records get updated and need to be unchangeable until the report is done) and then launches an R/List statement.
It appears that R/List automatically unlocks records as it reports against them. Is this correct? Is this necessary?
Thanks,
At 01 DEC 1998 03:05PM Warren wrote:
This is normal behavior.
1) Try EXECUTE vs PERFORM for the RList.
2) Try the (L) option on RList (works for recordcopy I don't know about list)
3) Try PUSH/POP_SESSION (I don't remember how to use this one so someone else will have to help you here).
At 02 DEC 1998 02:21PM Warren wrote:
Now that I had a little more time to think about it I remember butting my head against this exact same problem and 'design' years ago. If I recall there is no simple solution other than writing the report in RBasic and maintaining the locks programmatically. The source of the problem is that uses machine/station ids as part of the file/record locking scheme but does not use any session information for the locks.
At 02 DEC 1998 03:59PM Paul Simonsen wrote:
Thanks for the confirmation and ideas. I'll first try to switch my PERFORM to EXECUTE and then use the PUSH/POP method (I have documention on these or Don can probably show me).
At 02 DEC 1998 05:24PM [email protected] wrote:
Try as I might, I can't duplicate this.
What ARev version?
Are you running this from a menu or TCL?
Is the R/LIST statement latent or resolved?
Can you duplicate this on a smaller scale?
At 03 DEC 1998 01:01PM Warren wrote:
Aaron, I ran across this ages ago in v2.01. Since I've only run into a situation once where I needed to maintain locks during an RList (I got around it by writing the report in RBasic) I never checked to see if it occurs in other releases.
I just ASSuMed that this is normal behavior
.