Skipping Upc Check Digit Validation
We recently upgraded from Bartender 7.75 to Bartender 10.0.
We have an Microsoft Access based application that populates a SQL data table and then calls a Bartender label format to print a large batch of labels as part of an automated process. In our database, we store the entire UPC-A including the check digit.
It would appear that in our source data, we have some check digits that are incorrect in the data. When we called this label format using Bartender 7.75, it would print the entire batch of labels with no issue (although any records that included a bad check digit would produce a barcode that wasn't readable). After upgrading to version 10.0, Bartender encounters the error condition and stops printing the batch it is working on.
Is there any way to turn off that validation step in Bartender either in the program options, the label format itself, or by including a particular parameter when we call the process?
We have an Microsoft Access based application that populates a SQL data table and then calls a Bartender label format to print a large batch of labels as part of an automated process. In our database, we store the entire UPC-A including the check digit.
It would appear that in our source data, we have some check digits that are incorrect in the data. When we called this label format using Bartender 7.75, it would print the entire batch of labels with no issue (although any records that included a bad check digit would produce a barcode that wasn't readable). After upgrading to version 10.0, Bartender encounters the error condition and stops printing the batch it is working on.
Is there any way to turn off that validation step in Bartender either in the program options, the label format itself, or by including a particular parameter when we call the process?
0
-
[quote name='RiverValleyIT' timestamp='1346262050' post='3168']
We recently upgraded from Bartender 7.75 to Bartender 10.0.
We have an Microsoft Access based application that populates a SQL data table and then calls a Bartender label format to print a large batch of labels as part of an automated process. In our database, we store the entire UPC-A including the check digit.
It would appear that in our source data, we have some check digits that are incorrect in the data. When we called this label format using Bartender 7.75, it would print the entire batch of labels with no issue (although any records that included a bad check digit would produce a barcode that wasn't readable). After upgrading to version 10.0, Bartender encounters the error condition and stops printing the batch it is working on.
Is there any way to turn off that validation step in Bartender either in the program options, the label format itself, or by including a particular parameter when we call the process?
[/quote]
What you should do to resolve this is to configure truncation so that it's only receiving the first 11 characters (so that the program can generate the check digit). This is precisely what versions prior to 9.3 did, so if you want to keep the same process in place this is the best way to do that. To set that up, double-click on the barcode, then go to the transforms tab. Select the box next to 'truncation', then check the box that says 'keep characters on left' and set that to 11. Save the label, and when you send the info from your application it will only use the first 11 characters in the barcode, regardless of how many characters are actually being passed.0 -
[quote name='Mike T - Seagull Support' timestamp='1346348744' post='3172']
What you should do to resolve this is to configure truncation so that it's only receiving the first 11 characters (so that the program can generate the check digit). This is precisely what versions prior to 9.3 did, so if you want to keep the same process in place this is the best way to do that. To set that up, double-click on the barcode, then go to the transforms tab. Select the box next to 'truncation', then check the box that says 'keep characters on left' and set that to 11. Save the label, and when you send the info from your application it will only use the first 11 characters in the barcode, regardless of how many characters are actually being passed.
[/quote]
Thanks for that suggestion. That does sound like something that would work.
This morning we found another option that seems to have some promise. We were able to isolate that the program was throwing error #3752. In the application, we went to the "Message Setup" window under the "Administer" tab. The settings for error #3752 were set to "Cancel" when it encounterd that. We changed that instead to "Ignore" and the program seems to behave like it used to.
We were hesitant to change anything in the label format because we still have a mixed environment with Bartender 7.75 and 10 both still existing.0 -
[quote name='RiverValleyIT' timestamp='1346439637' post='3180']
Thanks for that suggestion. That does sound like something that would work.
This morning we found another option that seems to have some promise. We were able to isolate that the program was throwing error #3752. In the application, we went to the "Message Setup" window under the "Administer" tab. The settings for error #3752 were set to "Cancel" when it encounterd that. We changed that instead to "Ignore" and the program seems to behave like it used to.
We were hesitant to change anything in the label format because we still have a mixed environment with Bartender 7.75 and 10 both still existing.
[/quote]
Turning off the error message would work, just be aware that you will see those errors in your log files if you do that.0
Please sign in to leave a comment.
Comments
3 comments