Pushkey "[SAVE]" question

Don Coleman dcoleman at dgcreact.com
Wed Oct 10 10:47:22 PDT 2007


> -----Original Message-----
> From: filepro-list-bounces+dcoleman=dgcreact.com at lists.celestial.com
> [mailto:filepro-list-bounces+dcoleman=dgcreact.com at lists.celestial.com] On
> Behalf Of Kenneth Brody
> Sent: Wednesday, October 10, 2007 1:28 PM
> To: Barry Wiseman
> Cc: FilePro Mailing List
> Subject: Re: Pushkey "[SAVE]" question
> 
> Quoting Barry Wiseman (Wed, 10 Oct 2007 13:09:45 -0400):
> 
> >
> > Don Coleman wrote:
> >
> > [snip]
> >
> >>  111 -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -
> -   -
> >> @KEYR    If: CB eq "2"
> [...]
> >> 69="";85="";AG="";70="";71="";DF="";DP="";DV="";EU="";display;pushk
> >>              ey "[SAVE]";write;close;goto @ENTSEL
> >
> > Don, what led you to believe you needed the pushkey "[SAVE]" in the
> > first place?  In my experience, when @KEY processing is triggered,
> > that places you in update mode.
> 
> Correct.
> 
> > A simple END will then terminate processing and rewrite the record.
> 
> Also correct.  (Well, it will write the record if you made any changes.
> In either case, the record will be unlocked.)
> 
> > Are you doing something funny in @ENTSEL that the pushkey "[SAVE]" was
> > fixing for you?
> 
> Also, when @KEY processing ends, @ENTSEL will be run automatically, so
> the "goto @ENTSEL" is unnecessary.  (In fact, as Nancy partly mentioned,
> by not ENDing @KEY, and doing a GOTO @ENTSEL, you have prevented filePro
> from writing and unlocking the record.)
> 
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list


I agree with everything Nancy, Barry, and Ken have stated.  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.

  

Don Coleman
Donald G. Coleman, Consultant
402 Andrew Circle
Indiana, PA 15701
dcoleman at dgcreact.com
(724) 349-6302




More information about the Filepro-list mailing list