Thanks Bill, that illustrates it very well. I tend to think of / use screen as being a handy way to position the cursor, not a sort of shelling out process, so tt wouldn't be the behaviour I would intuit. <br><br>Tyler<br>
<br>Message: 1<br>Date: Fri, 17 Feb 2006 16:37:19 -0500<br>From: "William Randall" <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:wrandall@fptech.com">wrandall@fptech.com</a>><br>Subject: Re: GOSUB and SCREEN and closer reading....
<br>To: <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:filepro-list@lists.celestial.com">filepro-list@lists.celestial.com</a>><br>Message-ID: <08ac01c6340a$54fb4af0$cd00a8c0<div id="mb_0">
@bill64><br>Content-Type: text/plain; format=flowed; charset="iso-8859-1";<br> reply-type=original<br><br>I used this in a class that I gave to demonstrate filePro logic on the<br>screen command. If you try it, you might understand it better or you may
<br>just understand from reading it.<br><br>top:::<br>::msgbox "Now I am proceessing from the top of the table where I belong":<br>::end:<br>@keys:::<br>::gosub chkthis:<br>::msgbox "Made it back to where I started" ; goto top:
<br>chkthis:::<br>::screen "0":<br>::msgbox "I came back here":<br>::msgbox "I think I should return" ; return:<br><br>Bill</div>