RE: Varying length field issue

["Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>]

> I can't say that I remember seeing this myself.  But it seems 
> to make sense.
> 
> When you say
> Eval PrintInfo = *BLANKS
> 
> Just what do you what PrintInfo to have in it?  How many 
> blanks: 0,1,2,5,10, 100...?  I'd guess it is getting the MAX 
> length number of blanks.
> 
> Instead what you want is to set the field empty.  Try the following:
> Eval %len(PrintInfo) = 0

You're right that it makes sense.  I tried your suggestion and it worked
fine.  I've use varying fields in quite a few places before.  Guess I just
never had occasion where it was totally optional.

Thanks.

-- 
Jeff Crosby
Dilgard Frozen Foods, Inc.
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.