Sage 100

Sage 100 2014. I am trying to BarCode some regular text on a Picking Sheet so that shipping can scan the text rather than type it into Sage. I have been able to Barcode the Order Number & item Number using the formula provided in the Crystal Form and that works great, but I can't get the text to scan. It looks and prints like a barcode but the scanner does not read it. I tried the various Azalea fonts, Code128wide, Code128small, Code39, etc but nothing will pick up the barcoded text. Any ideas?

Have you opened note or wordpad and seen if it will scan in that app? Also, are your using the Crystal formula for the bar code and then changing the font?

@MoiraGoggin Yes, tried in Notepad and it does not scan there either. Not sure which Crystal formula you are referring to. Sage has some built in formula's but they are for Item Numebr, Order Number etc. Basically, I am creating a text field and changing the font to a barcode font. Also, tried right-clicking on the text field and selecting ""Change to Bar-Code"".

I am assuming you are printing on a laser printer. Thermal printers are different and if you use azalea it might not scan since the bar code is treated as an image and not a font and can be scaled in a way it doesn't scan. Lasers what I usually see the issues when the start and stop bits are not showing. This can easily happen if your field is not large enough to display the whole barcode. I would think if you are using the same method for creating the bar code as others on the form that this is the issue. If you google how barcodes work you will see some images that show what the start and stop look like. See if you see the the same in your barcodes.

Have you tried right clicking on the field on the form, and choosing ""Change to Barcode?

We have had some issues with a client where the dpi on the printer was too low and the actual barcoded value was very long and consequently the bars and spaces of the barcode were not distinct (they were bleeding together) making the barcode unreadable.

How long is the text field you are barcoding? Code 128 barcodes get big fast, and it is hard to get enough room to display the entire code. It is possible your gun has restrictions as well. I have had the best luck barcoding large text using 2D barcodes, specifically, PDF417. Be advised that crystal has limitations on how large the text can be as well. I seem to recall running into a limit around 60 chars in Crystal 10 - have not tried it in any new versions. FYI - The Azalea that comes with the system does not provide for 2D barcode generation. I use Wasp software because it has Crystal functions like Azalea, but I had to buy it.

@ToddMartin Yes, printing on the same laser and form where I have other BarCodes (Order Number, Item Number) which scan fine. I made the field very large but still not scanning. I wiil trygoogle and see what else I find.

@MadelineStefanou Yes, tried rght-click and choose Change to Barcode. Tried all the various font options that come up when you do that.

@RandyMarion Very simple text is what I am trying to scan. Basically, it's the name of the store placing the order i.e. Target, Saks, Kohls etc. I'll try Wasp fonts, I think I bought it many years ago.

If you do not see the start code or the stop code then you are still not showing the full barcode or you are not using the correct formula in crystal that creates the start and stop bit. The function in crystal will create the start the stop and the check digit for the value you wish to scan. In the sample below you will see the value is CSE370.The value should be what appears when you scan the barcode. You will also need to have quite zone before and after. The minimum width of the Quiet Zone to the left and right of the 128 Bar Code is 10x, where x is the minimum width of a module. It is mandatory at the left and right side of the barcode. The quiet zone must not be less than 4 mm-1.65 mm depending on the type of bar code.

Is your reader configured to read each of the fonts you tried? It sounds like it might be configured for Code 39, without Full ASCII enabled. You could test by converting your text in your labels to all uppercase. Code 39 will read digits and uppercase, but not lowercase as in your examples. To read lowercase, you would need to configure your reader to ""Enable Full ASCII"".

@KennyDaniel You have to use the same function calls that are in the BarcodeOrderNumber and ItemNumber formulas (i.e. Barcode128B). Just changing the font of text will only print unreadable images that look like valid bar codes, but they are not. You must use the integrated functions.

@DanBurleson How do I that? I tried using one of the existing functions and just replaced the field name with the Text i wanted but that did not work either.

I guess I have to do more testing and research. I'll be out there again next wek and will update. Thanks everyone.

Since you're doing text you will have make the field width large enough for the longest string in that field to be sure that the field isn't being truncated. Over widened it so that you are sure exactly how wide the longest bar code is. Then reduce it while ensuring you don't lose the patterns that are the stop/stop bars at either end.

In summary - use the proper crystal function to generate the barcode, use the proper font that corresponds with the function used and make sure you have plenty of space allowed for the field to display in the report. If your gun is reading other barcodes different reports are printing, examine those functions and fonts used, then you know the gun is functioning and configured for those symbologies at least... You should be able to make them work for store names. Finally, is you do install Wasp, use Wasp fonts w/ Wasp functions and Azalea w/ Azalea. Hope this helps