Posted by Bob A on October 15, 2012 at 13:53:50:
In Reply to: Re: has anyone tried to use @(SET variable) in a print line? posted by Barbara Brazil on October 15, 2012 at 13:12:42:
BB:
In retrospect... I fully understand that this could be confusing
this is a pick slip printing program...
I ran it twice with two different work orders to pick
the first one is on the top
the second is on the bottom
same program at the same time.... can't figure for the life of me why this wouldn't line up
copied the pick tickets to UE... looked at it in HEX.... saw that the offending characters were "@20@" and that is why the printing wouldn't line up
checked the files in COMETEX.... there are no data elements shifted over (i.e. leading "@20@")
can't for the life of me figure this out as it's the same program at the same time...and yet one print line has extra blanks in it
the only thing I changed (I think :) from the original program was that it had "hard coded" offsets like @(24) instead of SET offsetOrderNumber = 24 and than down in the FORMAT statment @(offsetOrderNumber)
It's a Comet16 compile run under Comet32
I will confess in advance that I'm surely exercising parts of the compiler that other's don't. My only reason for putting the offsets in SET statements is that I'm going to have to adjust this a few times to get it to work.
FWIW.... Grant suggested that he only uses the offset first as in @(23);OrderNumber$
Thanx
Bob "A"
P.S. in the original, there were mystifying things like: (I'm really confused what the leading and trailing underscores accomplish).... similarly why there are two fields (RCVID$ and DSERNBR$) that are then overlaid with ODESC$ what does this accomplish?
2850 FORMAT__
OQTYORD,@(0);__
INBR$,15,@(9);__
__ RCVID$,@(25);__
___ DSERNBR$,@(42);__
OPRICE,@(59),"####0.0000-";__
OEXT,@(70),"######0.##-";_
ODESC$,@(25)
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.