Pushkey "[SAVE]" question

[Kenneth Brody]

Quoting Don Coleman (Wed, 10 Oct 2007 13:47:22 -0400):
[...]
> I agree with everything Nancy, Barry, and Ken have stated.

Sounds like a good policy.  :-)

>  However, this
> AM, before I made any changes (after observing the record lock) the
> processing went as such:
>
> Pushkey "[SAVE]";end
>
> This caused a record lock. I then changed it to:
>
> Pushkey "[SAVE]";write;close;goto @ENTSEL
>
> Still locked the record
>
> After seeing Barry's suggestion I changed it to just:
>
> End
>
> This unlocked the record and @ENTSEL ran automatically after the "end" as
> suggested.
>
> I guess I don't understand why the pushkey "[SAVE]";end did not unlock the
> record.  Thanks for the advice though.

Without seeing the actual processing, I can only guess that something in
your @ENTSEL processing does something if it sees SAVE.

I'm not sure why you felt it necessary to include the pushkey in the first
place, but it shouldn't cause the record to remain locked.  It is certainly
possible that something in your @ENTSEL causes the record to be re-locked
at some point.

Is this a *nix box?

Can you put back the original version (with the pushkey), and single-step
through the debugger in one window and run showlock in the other to see
when/where the record is locked/unlocked?

What about keeping the non-pushkey version, but after running @keyR (which
now "works" in that it unlocks the record) and returning to @ENTSEL, press
SAVE at the keyboard and see if the record re-locks.

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com