@WEF. @WLF in @ENTSEL

[Boaz Bezborodko]

>
> Date: Fri, 21 Sep 2007 12:05:39 -0400
> From: Barry Wiseman <barry at gensoftdes.com>
> Subject: @WEF. @WLF in @ENTSEL
> To: filePro list <filepro-list at lists.celestial.com>
> Message-ID: <46F3EBD3.2030405 at gensoftdes.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Further adventures in my quest to keep the current record unlocked:
>
> In the course of my @ENTSEL processing, I have
>
> ::popup update -,"ADD":
> :@sk eq "BRKY":goto @entsel:
> ::pushkey "A"; end:
> @KEYA:::' now we're in update mode, post the data from the ADD screen:
>
> The ADD screen contains only global dummy fields.  Pressing BREAK will take down the 
> popup and leave me at the primary screen of the current record, as expected.
>
> However, I want to use @WEF and @WLF processing on this popup update screen.  These 
> processing chunks are for on-the-fly "Amount = Quantity * Price" type calculations, 
> and do not write any real fields.
>
> As soon as any @WxF processing has been triggered, a subsequent BREAK will then 
> entirely exit me from dclerk instead of performing the "goto @entsel".
>
> Is there a way this can work?  TIA.
>
> -----------------------------------------------------------------
>   Barry Wiseman                              barry at gensoftdes.com
>   Genesis Software Designs, Inc.            Voice: (212) 889-9191
>   55 West 45 Street, New York, NY 10036       Fax: (212) 889-1589
If you are so interested in keeping the record out of update mode then 
why not work from a separate, duplicate file (or even just a separate 
qualifier)?  When selecting the record to work with COPYIN the data to 
the new working record.  Once you're ready to update any particular 
piece of data you update the original record.  The original file is only 
open very briefly for the updates.  When you're done you simply delete 
the separate working record.

Boaz