waiting for foobar record nnnnn to be unlocked

[Richard Kreiss]

> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-
> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Kenneth
> Brody
> Sent: Thursday, January 29, 2015 2:13 PM
> To: Richard Kreiss; Filepro List
> Subject: Re: waiting for foobar record nnnnn to be unlocked
> 
> On 1/29/2015 1:25 PM, Richard Kreiss wrote:
> > I send a follow-up post and a called routine from transaction is
> > trying to write back to foobar.
> >
> > I need to come up with a way to close the foobar record, run the
> > transaction routine and bring the user back to the foobar record on
> > screen 9 as that seems to be the only solution to this problem.
> >
> > That looks like it will be "fun" to program.
> [...]
> 
> What do you mean by "close the foobar record"?

Since the program is trying to write to the foobar record where the browse
is active, the record is locked.

To have the transaction program work properly, it needs to write back to the
record where the browse is open.  Therefore, the foobar record needs to  be
in update mode (locked by activating the browse form @key9).  It will have
to be closed to allow the transaction program to write back to it.

The problem is how to exit the browse, run the transaction program and then
bring the user back to the same record preferably on screen 9 with the
browse open.

I may need to create a batch file which is run when the option to run the
transaction process is selected.  I will have to write the record number to
a file to be read in on the return and have an input process that moves the
user to the proper record and opens the browse.  The program, on exit, would
chain to the regular input process.

I am curious if you have a better way of doing this.  You thoughts would be
appreciated.

Richard
> 
> 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.)
> 
> --
> Kenneth Brody
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list