Hey everyone,
I need to make the Assembly Sequence field print as a barcode. All the values that print as barcodes when we select the print barcodes check box on the Job Traveler report are showing up and scanning just fine.
However, when I change the font on the AssemblySeq field to DataWorks barcode 39 (Like the other fields showing up as barcodes) it does appear to print as a barcode, but it will not scan.
The Barcode highlighted below is the one i changed in font but won’t scan. Any ideas?
I had this problem many years ago… the problem is that the scanner doesn’t like it because it is too short… my solution was simple. I zero filled the field… assembly 1 became 001, and the scanner would then see it.
Also make sure that you have the Asterisks as part of the barcode… ie…
Ordinarily you would just create an expression inside the layout, if you wanted to do it that way, and just concatenate the asterisks, which is the start and stop character typically for the 3of9 barcode.
For example, every code that you see will start and end with:
Inspect the bars and you can see it.
From your ASM, it looks like it has just enough ‘space’ to show you the starting asterisk. Probably just need to ‘resize’ the field in the layout so that you can see the entire barcode.
First, note that in order for the Code 39 barcode to be scannable, it must include the start and stop character, which we establish as the asterisk, and it looks like this:
So, with that pattern of thin-space-thin-thick-thick-thick, we can see in the job traveler example that you posted, we can see that pattern appearing.
So, that should tell us that the Assembly Sequence field already has at least the asterisk in it already. With that information in hand, open up the RDL and have a look at the field definition. You are looking for the Properties to see something like this:
Or:
In my case, the Value is indicating that the report is already using a Field that is a calculated field and is assumedly already prepped for use as a barcode.
Calc_BCAsmSeq.Value
@Michael_Ramsey My mistake. I should have read your response more carefully. I had the following - Fields!AssemblySeq.Value. I did try to change it to the Calc field you have in your report, but it would not scan for me. I did not drag it from the dataset however, I changed it by clicking on the blue icon that appears on the top right side of the text box when you are hovering above it. It may have been related to what @timshuwy was saying about the length. Maybe it just did not have enough to register (the first assembly I was testing was assembly 0). I ended up getting it to work with the Fields!AssemblySeq.Value by formatting it as =format(Fields!AssemblySeq.Value,“000" &"”). This way it would always have at least three numbers and it would always carry the asterisks.
there is supposed to be an asterisk before the first zero and in-between the last two quotation marks. Like shown in the picture below.
If you go back to the vendor version of the report, you should see the barcode fields available already there and you can see how they did it. Unless for some reason in your version it was not there.
