Sage 100

 View Only
  • 1.  I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 07:31
    I have a client that upgraded from 4.5 to 2017. They print barcoded employee numbers for scanning on/off labor. When they print the barcode from 2017 to a zebra printer, the scanner does not register the barcode. It prints fine/looks the same. The same exact employee number/barcode printed from 4.5 works. It also works if they print the barcode from v2017 to a laserjet printer on regular paper. I am assuming its an issue between Crystal/Zebra - what can I do to fix? I'm not sure if updating the driver for the Zebra would help.


  • 2.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 07:48
    Did you install the Azalea font (C128Tools) that is under wksetup?


  • 3.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 07:57
    The font is actually a formula. that may have been updated with the newer version of Crystal. It looks like a regular barcode but is missing the bit that makes it a readable barcode without the correct formula.


  • 4.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 07:58
    Azalea is installed. The barcode is readable with my phone, and when it prints to a laser jet.


  • 5.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 08:22
    I think you have to enclose the field to bar code inside of a bar code formula. Check the 4.5 form and specifically the formula used to print the barcode you can scan in 4.5. I think @alanniergarth is correct. Even though the barcode looks fine I was not able to scan until I used the formula to convert to a bar code readable format.


  • 6.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 08:33
    It's converted with the formula.


  • 7.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 08:34
    I used formula = BarcodeC128B ( { field name} ) We are using cheap no-name scanners and once I did that I was able to read it.


  • 8.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 08:35
    Font Code128Wide / 36 point (not sure if that makes a difference)


  • 9.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 08:36
    Sorry, I missed that this is likely a zebra issue since you can scan fine from plain paper/HP printer


  • 10.  RE: I have a client that upgraded from 4.5 to 2017. T

    Posted 12-08-2017 10:35
    Check that it is not being chopped short when printed on the labels. Each valid bar code has start / end characters which must be fully printed to scan properly.