Jim,

        VPUTSAVEFIELD will do what you expect it to. What Gopi is saying that it
will not do, is modify the initial value that is saved in the forms file.
You know, that screen where you create a save field and assign it an
initial value. Put another way, the save field value will not be saved
across different executions of the program.

-John Zoltak
North American Mfg. Co.
Cleveland OH 44105

Jim Phillips <[log in to unmask]> wrote in article
<[log in to unmask]>...

> Maybe I am being incredibly dense here, but I'm still not clear on
> this issue. I use save fields in forms files to save data between screens
> (like an order number, for instance) so I can use the INIT processing
spec
> to put the saved value into a field on a new screen; thereby
"remembering"
> it for the user.  VGETSAVEFIELD would retrieve the saved value for me
> (my application) so I could "know" the value of the save field before the
> screen is displayed and (perhaps) retrieve additional data to display to
> the user, correct?
>
> But what is the purpose of VPUTSAVEFIELD?  If, for instance, I display
> a screen, the user enters an order number, and I do a SET in the
processing
> specs to store the value in the save field.  The next screen I display
> has a SET <field> TO <save field> in some field's processing specs.
> Now if I call VPUTSAVEFIELD and change the value of the save field
> before I display the second screen, what value is displayed?  The save
> field value that was entered on the previous screen or the new value
> that I changed it to using VPUTSAVEFIELD?