More specific question on @SK

[Kenneth Brody]

Okay, since I've only gotten one (partially-incorrect) answer off-list, and 
two vague attempts at answers on-list, here is my more direct question.

Given the following processing[1], what would you expect to see on-screen 
when you press [SAVE] on a field?

==========
TheTop   If: @sk = "save"
     1  Then: mesgbox "Here we are at TheTop with SAVE" ; end
          If:
     2  Then: mesgbox "Here we are at TheTop with @sk='" & @sk & "'" ; end
@wlf*    If: @sk = "save"
     3  Then: goto TheTop
          If:
     4  Then: end
==========

No fair actually running it in filePro until after you answer.  If you want 
to run it afterwards, you are free to do so.  If what you see doesn't match 
your expectations, explain what differences you saw, and explain why you 
thought your answer was correct.


[1] Assuming all defaults are in place.[2]
[2] To prevent any "but what about this scenario" questions, I mean the 
following:
     The file is named "foo".
     There is a single real field, defined as bar(1,*).
     The file has one record in it, created by dexpand.
     No one else is using the file.
     No command-line flags were passed to dclerk.
     No other processing, whether automatic or input, is in use.
     The user selected the ddefine-generated screen 0.
     The user chose record-number mode, and went to record 1.
     The user pressed "U" to enter update mode.
     The user then pressed [SAVE].

-- 
Kenneth Brody