Issue with Bartender 2022 and MariaDB: QR Code Printing
Hello Community,
I'm encountering a challenging issue while using Bartender 2022 to print QR codes from a MariaDB database. I'm hoping you can provide assistance or share insights on this matter.
Problem: I'm linking Bartender 2022 with a MariaDB database to generate QR codes. In the database, the ID column of the Assets table definitely contains data, but when pouring the data into the QR code, Bartender displays it as empty.
Specifics:
- Using MariaDB as the database.
- Linking with Bartender 2022 to create QR codes from the ID column of the Assets table.
- Values in the ID column all have valid data.
Specific Issue: When printing, the QR code appears empty, even though the database contains valid data.
Questions:
- Has anyone encountered a similar issue when using Bartender 2022 and MariaDB?
- Are there any troubleshooting steps or solutions to ensure that data from the database is accurately populated into the QR code?
I greatly appreciate any help and insights from the community. Thank you!
-
I take it you set/linked the QR code sub-string to get the data from the correct field in the database?
What happens if you add a text string onto the label linked to that field, is it populated?
1 -
First and foremost, I would like to express my gratitude to Mr Peter Thane for sharing and posing such insightful questions.
I've attempted to use the CONCAT function in the SELECT statement to append the text "http://xxx.xxx.xxx.xxx/hardware/" before the assets.id column, and the data displayed correctly on the QR code. I appreciate Mr Peter Thane's suggestion in this regard!
However, I encountered a challenge where the raw data from the assets.id column, without the additional text, resulted in an empty QR code. It raises the question of why the original assets.id data alone doesn't populate the QR code correctly, and adding extra text is necessary for proper display. I'm putting this question forward in the hope of gaining a deeper understanding of the root cause.
Regarding my inquiry about the assets.id column being formatted as int attributes Unsigned in the database, I'm curious whether this format could potentially affect data detection. If there is any information or shared experiences from the community on this matter, I would greatly appreciate the insights to get a more comprehensive view of the issue.
Thanks to everyone for taking the time to read this, and I look forward to receiving further sharing and opinions from all of you!
0 -
Does the data change from numeric to alpha numeric or alpha characters only in the column?
May not be the same but I have come across something similar a few times where the ODBC driver that forms the link between the database and BarTender ignores the formatting/data type set in the database itself and looks at the first few records only and determines this itself. So if the first few records are all numeric then any that contain alpha characters later appear as blanks as the ODBC driver has determined that this is numeric only column.
Reordering the records in the database or else adding a say a record where all the fields contain the word dummy or test will get round this.
1 -
All data entries in the "assets.id" column are numeric, with no text characters. Another observation is that when primary keys in the table are selected for data linkage, they appear as empty if not concatenated with a text string!
0
Iniciar sesión para dejar un comentario.
Comentarios
4 comentarios