Re: Moving a field and removing blanks

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Yeah, Kurt - I'd lost track of the original intent - mea culpa!

Vern

On 12/1/2010 9:28 AM, Kurt Anderson wrote:
> If you have a field the following field:
> FIELDA = "1234     "
>
> And you want to put 89 at the end to give a value of "1234   89", then saying EVALR FIELDA = '89' is not going to do it.
>
> All of the substring solutions appear fine.  I was just taking issue with Vern's statement to ignore using the substring functions and simply do plain EvalR (as per his example).
>
> -Kurt
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
> Sent: Wednesday, December 01, 2010 9:07 AM
> To: 'RPG programming on the IBM i / System i'
> Subject: RE: Moving a field and removing blanks
>
> All of these solutions will, as far as I can see.  If they don't the result won't be as sought.  Do you really care that the field is momentarily blank, since there's no chance to intercept it in that condition?  Or maybe I don't understand your objection.
>
> Dennis Lovelady
> http://www.linkedin.com/in/dennislovelady
> --
> Shin bone: (n) A device for finding furniture in a dark room.
> > However the OP wanted to retain data that is in the result field.
> > Eval or EvalR will clear the field before assigning the value.
> >
> > -Kurt