I ran into an issue similar to this, though not related to Code 128.Turnsout the Unicode character code (number) for my character was simplydifferent in a Unicode environment from before, in a pre-Unicodeenvironment.

Take an existing Code 128 barcode, scan it, and using 4D parse thefirst fewcharacters. ¬=A0You might find that while the code was created withchar(143) in a non-Unicode enabled 4D, when you read it back in aUnicodeenabled 4D, it is some other character code.

Hopefully it is that simple, and you can simply substitute the newcharactercode for 143 in your code that creates future barcodes.

I ran into an issue similar to this, though not related to Code 128.Turnsout the Unicode character code (number) for my character was simplydifferent in a Unicode environment from before, in a pre-Unicodeenvironment.

Take an existing Code 128 barcode, scan it, and using 4D parse thefirstfew characters. ¬=A0You might find that while the code was createdwithchar(143) in a non-Unicode enabled 4D, when you read it back in aUnicodeenabled 4D, it is some other character code.

Hopefully it is that simple, and you can simply substitute the newcharacter code for 143 in your code that creates future barcodes.

HTH,

Bob MillerChomerics, a division of Parker Hannifin CorporationReply to this messageSummary created 5/16/14 at 1:14PM by Intellex Corporation