waiting for foobar record nnnnn to be unlocked

[Kenneth Brody]

On 1/29/2015 12:30 PM, Richard Kreiss wrote:
> User on a record in foobar
>
> When 9 is pressed the screen changes to screen 9 and the user is placed
> into a browse of the transaction file associated with that record. The
> use can selects one of the transactions and a system command executes to
> run an output program.

Am I correct that this is done via @key9?

> That program in turn executes a system command and runs a program to
> process the information send and read back the response.
>
> All of this works nicely until the program tries to return to foobar and
> re-read the browse.  That's when the record lock error occurs.

Is that process attempting to lookup the record which you are updating from 
the first program?

I'm also not clear on the vague "run an output program", "runs a program", 
"return to foobar", and so on.  Can you please be explicit on what program 
calls what command, and which program is the one giving the error?  ie: are 
you back at the original dclerk?  Still in the dreport(?) called by that 
dclerk?  Some other program entirely?

> The only time the transaction output program access foobar is a lookup to
> read some information from the record, it does not post any data back to
> that record.
>
> Is there a way to avoid this problem as I need to return the user to that
> record and browse so they can see the result?
>
> When I tested the routine without doing the second system from the
> transaction file, I did not lock the record on return.

-- 
Kenneth Brody