We have tried hard to insert the barcode (code 39) to our print contexts. However, the barcode on the generated PDF file is not working at all with cashier scanner. Do we need a special scanner for the PDF file? Our current scanner has been working fine with the AFP printouts and I am wondering if it is still working for the PDF file generated with Planet Press designer.
this should work with your cashier scanner. When you print the PDF from Acrobat, be carefull to keep the original size of the page. If not, it could be reduced and barcode no more readable.
You can also try to read it with a smartphone to check if it’s correctly made.
Maybe your scanner needs that you change the barcode module width or the inter character gap. Try to modify a bit those values and check if the scan is better.
The code 39 type string (like *51504719150000000233859) we are pulling out from our backend is generated with other application. I was just trying to plug it in to the Planet Press designer. I am wondering if I could use the INSERT to plug in an existing barcode. is the INSERT trying to generate a new barcode or just plug in an existing barcode?
Nope, Yann, I meant I had a barcode 39 type string like 51504719150000000233859 fro each bill generated by a SQL stored procedure. The roll_number and balnaceAmount have been embedded in that string.
You’re correct, Yann, the * character should be trimmed from the original string. But I run into another problem. The amount is showing up always as zero. It seemed to me that the amount 233859 should not be the data type of string.
You cannot use * as data to generate the barcode because Code 39 don’t accept it, see http://en.wikipedia.org/wiki/Code_39. * character is automaticaly added in the barcode itself.
If you get an extra character on the string readed, this is because you must have selected to add a checksum. You can select IGNORE for the checksum to have the result you want to.