Sage 100

Sage 100 2016 (Crystal 2011) barcode 128 only prints a ""P"" paragraph symbol, not barcode. I'm printing barcoded items on the PO form for Scanforce scanning. When I use change to Barcode 39 on the item number field, it scans great. Except that any item with a pound sign ""#"" has trouble. It converts the # to /C. I installed the Azalea CT128 toolset, so I see the Azalea options for Code 128. I used the premade crystal formula field for barcoded item number with the barcode 128B function in the formula. I right clicked on the field and selected the option to change to barcode and selected code 128B. It displays as a barcode in the crystal design screen, but when I exit and print out the PO form, it only shows the paragraph symbol for the barcoded item number. All I want is for a # to scan as a #. We had the discussion about using special characters in the item number field over 10 years ago, so that is not currently an option.

Did you set the font for the formula to ""Code128Wide"" like in the attached image? In the formula, are you using the function named ""BarcodeC128B""? Also, every workstation that will be printing the form with the code128 barcodes will need to have the azalea code128 barcode fonts installed. This is very important.

Sounds like you don't have the Azalea font on the workstation you are printing from. If it can't find it, it will replace it with the default. If that happens, you would usually see the Paragraph symbol at the beginning, if defaulted to Arial, followed by your data and some closing symbols like A with two dots on top. This is the start and stop bits of the barcode.

Clark in addition to what David said: 1) Sounds like Azalea font is not installed on the specific workstation you are at. So repeat the Azalea toolset install. 2) When you install Azalea toolset, it will also come with a handy dandy utility you can test with the scanner. Forgot the name but it's mentioned on C128ToolsDocumentation.pdf in the \mas90\wksetup\Azalea\Doc folder. When you run it, choose Codeset B, type in your part number in the top textbox. note the current Font name (eg.. ""Code128VeryWide"") then click on Preview. Now click on Copy then paste into Word or Wordpad and jot some notes in there. Now change the Font name to say Code128Wide and copy / paste again. Then to Code128Regular and Code128Narrow. Then finally print out your Word / Wordpad doc to the printer and attempt to scan each one. Note which ones work and don't work with the scanner, and which ones look like a good sized fit to print on the PO form. Then set the font in Crystal PO form to the one you chose (e.g. Code128Regular)

In addition to what Alnoor said, which are all good points, the reason for this is your mileage may very with different combinations of the font size and version of the c128 font (narrow, wide, etc) depending on the printer used. If you are printing to something like a zebra printer with 203dpi or similar, you will likely need to use code128, code128Wide, or code128VeryWide and a font size starting at least at 36 (possibly 24), and increment by 4, 6, or 12 points until you find a barcode that scans reliably. If printing to a laserjet or equivalent with 300 or 600 dpi, you can usually get away with a combination of any of the 5 code128 fonts and a font size smaller than 36 but try to stick to increments listed above. You can also refer to either of these links for really good info regard font size and barcode font. https://www.idautomation.com/barcode-fonts/code-128/user-manual.html http://www.azalea.com/white-papers/how-to-size-barcodes/

It's working now. I re-installed the CT128tools, and used the regular item number field, not the formula BarCodeItemNumber. I think there was also an issue where I needed to back completely out of PO printing and go back in. When I did that, everything worked as expected. Code 39 appears to convert a # to /C, but code 128 scans it without error. Thank you all for your help. After being out to the Sage world for a few years, some of my memory cells seem to have gone dormant. This helped.