Re: Scanning 2D barcode to Display File

[Booth Martin <booth@xxxxxxxxxxxx>]

Avoid barcode reads directly to the display screen fields. Barcodes 
generally have to be decoded, descrambled, etc.  Its been a while but I 
think I used a non-visible screen field on the display that is defined 
like the barcode, and scanned the barcode in to that.  Then process that 
field, sub-stringing out the positions you want and ignoring the unknown 
& unwanted.  I used a data structure with overlays and reassembed the 
useful segments in the order and layout needed.

Is there reason to worry about translating pipes when all you are going 
to do with them is ignore them?


On 4/16/2019 7:38 AM, Michael Schutte wrote:
> We have the same issue.  I discovered that the display files did not like
> the group separators (GS).  I had programmed the RF guns to translate them
> to pipes "|".   For us, the group separators were destroying the display,
> tying the user up where they couldn't do anything anymore.  Sorry about
> being vague, I'm sure what to call it.   That was with a GS-1 barcode.
>
> Now we are venturing into the 2D barcode and I suspect that we will have to
> do the same thing with translating the GS codes into pipe symbols that the
> display file can handle.
>
> We are using StayLinked on our RF devices if that makes any difference to
> you.
>
> On Mon, Apr 15, 2019 at 11:30 AM <SReeves@xxxxxxxxxxxxxxxxxx> wrote:
>
> > I'm trying to determine how to scan a 2D barcode to a field on a display
> > file.  Currently when I scan to the field, it seems the field separators
> > within the 2D barcode are causing the screen to continue as if pressing a
> > key.  So I only end up with with first field within the barcode and not
> > the entire contents.  Is there a keyword or some compile option needed to
> > prevent this?
> >
> > Thanks