Running a system from @entsel

[Kenneth Brody]

On 1/30/2015 2:22 PM, Richard Kreiss wrote:
>> -----Original Message-----
>> From: Kenneth Brody [mailto:kenbrody at spamcop.net]
[...]
>> What do you mean by "close the foobar record"?
>>
>> Going back to your original post, I am assuming you mean "get out of update
>> mode on the record the user is sitting on when he pressed '9' and triggered
>> the @key9 event"?
>>
>> If that's the case, the answer is simple -- use @entsel, which is run with the
>> user not in update mode, rather than @key, which is run with the user in
>> update mode.  (Use @key9 to set a flag, and end.  Check that flag in @entsel
>> and do what needs to be done.)
>

> Thanks for pointing me in the right direction. Had not thought of doing
> this. I'll bet a lot of others had not considered this option to avoid the
> locked record problem.
>
> When the @bk = "R" option is run, I am setting the variable for @entsel,
> doing a CLEARB;CLEARS and then and end. At @entsel if the variable is set,
> the program does a goto the routine which executes the system command. On
> return the browse is re-executed.

You have two conflicting pieces of information in your posts, for which I 
need you to answer a question I posed early on:

     Which record is locked?

Is it the record from the browse lookup?  If so, then the fact that you're 
in update mode is irrelevant.

Is it the record you're sitting on?  If so, then the state of the browse 
lookup is irrelevant.

-- 
Kenneth Brody