Process bypass

[Rami Mantoura]

That does sound like the issue because I changed my could so that the @wef
was not the first thing it does and it works.

Rami

On Fri, Sep 28, 2012 at 9:21 AM, Kenneth Brody <kenbrody at spamcop.net> wrote:

> On 9/27/2012 5:19 PM, Rami Mantoura wrote:
>
>> OK, Let me try...
>>
>> Menu Item "rclerk gwotoday -s1 -h "working"
>> We go into add records. Its starts with auto of course and at the end of
>> that it goes to input (by itself of course)
>> wef10: chain "chscr1". We are now on screen 1, field 10. We enter data.
>> and
>> when done we hit esc esc. It should at that point go to the top of chscr1
>> table (at least that is what is supposed to do). Thats what it does on old
>> system. Instead it jumps straight to auto and leaves me on the screen in
>> field 10. If I create the second record then it does what it is supposed
>> to
>> and goes to the top of the chscr1 table.
>>
> [...]
>
> I found a pending task item (#1039) that sounds like what you're running
> into.  If you execute the CHAIN from @WEF/@WLF processing, then the first
> time you save the record after that CHAIN, input processing will not be
> run.  Subsequent update/save will run the new input processing.
>
> --
> Kenneth Brody
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20120928/5752365b/attachment.html