waiting for foobar record nnnnn to be unlocked
Richard Kreiss
rkreiss at gccconsulting.net
Thu Jan 29 09:30:29 PST 2015
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.
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.
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.
Richard Kreiss
More information about the Filepro-list
mailing list