Inconsistent QR Code Rendering in Sage 100 Crystal Report

Question

We are using the QR Code Font and Encoder, specifically the Crystal Reports Font Formula generator in Crystal Reports, with the included 2D font and below is the code that fills the data variable. In 95% of the cases, it works just fine. We are now having an odd occurrence where specific values in the Salesorderno field are causing the QR not to render correctly. To prove that we copied the Failed SO into a new SO with a simpler SO# and it worked: X938322 failed SDLT11 worked We originally thought this meant that the overall string was too long. We proved this to not be the case by shortening another segment in the string. We tried increasing the font size, no dice. DataToEncode = {SO_SalesOrderDetail.SalesOrderNo} & "|" & {SO_SalesOrderDetail.ItemCode} & "|" & strDims & "|" & strTag & "|" & totext({SO_SalesOrderHeader.ShipExpireDate},"MM/dd/yyyy")

debrac · Accepted Answer

The observations I have:
1) It's possible that the space provided for the barcodes that have one additional character is not large enough, as QR Codes get larger when additional data is entered.

2) What is the point size of the IDAutomation 2D font? Make sure it is large enough for the scanner to read it. I've used 12 points in my barcode example, and the valid point sizes are listed here: 2D Universal Font Specifications.

3) Make sure that you have enough white space around the barcode and are using a valid point size for the 2D font to start with. To meet official ISO specifications, a QR code requires a "quiet zone" of blank space on all four sides measuring at least 4 times the width of a single data module (the smallest black or white square inside the code itself).

I also am unable to scan the examples that aren't working for you. I see that you are using our Barcode Font Encoder Formulas for Crystal Reports, and when I use your exact data from the top example, it is working correctly for us, so I cannot reproduce the issue.

"SDLT9SD|SFST603015-RW|60X30X15|SEL|02/19/2026"
Encoded data:

Resulting barcode:

SteveLimer11 · Answer

Regarding what happened, the ones that failed would not scan at all. Thoe ones that worked were complete.


debrac Best Answer The observations I have: 1) It's possible that the space provided for the barcodes that have one additional character is not large enough, as QR Codes get larger when additional data is entered. 2) What is the point size of the IDAutomation 2D font? Make sure it is large enough for the scanner to read it. I've used 12 points in my barcode example, and the valid point sizes are listed here: 2D Universal Font Specifications. 3) Make sure that you have enough white space around the barcode and are using a valid point size for the 2D font to start with. To meet official ISO specifications, a QR code requires a "quiet zone" of blank space on all four sides measuring at least 4 times the width of a single data module (the smallest black or white square inside the code itself). I also am unable to scan the examples that aren't working for you. I see that you are using our Barcode Font Encoder Formulas for Crystal Reports, and when I use your exact data from the top example, it is working correctly for us, so I cannot reproduce the issue. "SDLT9SD\|SFST603015-RW\|60X30X15\|SEL\|02/19/2026" Encoded data: Resulting barcode: Posted 102 day(s) ago (0) (0) Report Abuse