<div>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.</div>
<div> </div>
<div>Rami<br><br></div>
<div class="gmail_quote">On Fri, Sep 28, 2012 at 9:21 AM, Kenneth Brody <span dir="ltr"><<a href="mailto:kenbrody@spamcop.net" target="_blank">kenbrody@spamcop.net</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div class="im">On 9/27/2012 5:19 PM, Rami Mantoura wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">OK, Let me try...<br><br>Menu Item "rclerk gwotoday -s1 -h "working"<br>We go into add records. Its starts with auto of course and at the end of<br>
that it goes to input (by itself of course)<br>wef10: chain "chscr1". We are now on screen 1, field 10. We enter data. and<br>when done we hit esc esc. It should at that point go to the top of chscr1<br>table (at least that is what is supposed to do). Thats what it does on old<br>
system. Instead it jumps straight to auto and leaves me on the screen in<br>field 10. If I create the second record then it does what it is supposed to<br>and goes to the top of the chscr1 table.<br></blockquote></div>[...]<br>
<br>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.<span class="HOEnZb"><font color="#888888"><br>
<br>-- <br>Kenneth Brody<br></font></span></blockquote></div><br>