Ann,
I have setup Symbol scanners in Vantage. These are the characters
reserved for special functions: % $ ! @ # ^ & ( ) = { } | \ : ; " '
< > ? *
Andy Berg
National Tube Form
260-478-2363
I have setup Symbol scanners in Vantage. These are the characters
reserved for special functions: % $ ! @ # ^ & ( ) = { } | \ : ; " '
< > ? *
Andy Berg
National Tube Form
260-478-2363
--- In vantage@yahoogroups.com, "amfabllc" <amfab@...> wrote:
>
> I don't have much experience with barcodes, but have been able to
> create a few labels I need.
>
> A particular field that is barcoded on my label is the PONum.
> Everything reads fine - except if they use spaces, slashes, and
> sometimes dashes. What I mean be sometimes dashes, the dashes
seem
> to read OK on the PartNum field, but for some reason it won't read
> on the PONum field for my current project. These are formulas
that
> Calvin helped me with eons ago, I've just used his
formulas/formats,
> according to if it is a value or character, and changed fields in
> the formula as needed.
>
> When cust service creates an order for an RGR, they use the PONum,
> space, slash, original order number and line number, ie:
> p213695 /019220-11. Just recently became a problem since we have
to
> attach a barcode label to all parts to a particular customer.
>
> Just to check, I ran the label with just the PONum p213695, reads
> fine. The ones I tried that it will not read is p213695 /019220-
11,
> p213695/019220-11, p213695-019220-11.
>
> Does anyone know what characters and symbols are not going to be
> readable on a barcode, or if there is something I need to be aware
> of in the formula or format: Dataworks bar39, size 20, "*K" +
STRING
> (PONum) + "*"
>
> Thanks much!
> (Also, Thank you to Shirley Graver & Michael Podlin and all others
> for your recent help!!)
>
> Ann Rohyans
> Dexter Chassis Group
> formerly AMFAB
> 574-970-3269
>