BarTender Labels connection to ODBC in MAS but Query entry creates errors

Sage 100 ERP

Sage 100 ERP
Welcome to the product group for Sage 100 ERP. Share discussions, questions, and best practices with other Sage 100 ERP users. Sage 100 ERP is the most comprehensive feature-rich management suite for mid-sized and smaller distributors and manufacturers.

BarTender Labels connection to ODBC in MAS but Query entry creates errors

This question is not answered

Setting up receipt and inventory labels thru BarTender for a DataMax Thermal printer as using the crystal label within Sage 100 Advance 4.5 creates a second blank label each time it prints.  Since thermal printers are not supported and looking at various threads I had found that BarTender was a suggested software to create and print the label from Sage 100.  But after creating the label and creating the connection with Sage 100 I can see the data in the tables but when a query is created an error appears immediately and when it is cleared the next error says the ODBC path is not available.  But when there is no query then all items can be printed or if in the print field you can check the field you want to print.  But for this I need to be able to use the query for the area the printing will be used.  I contacted the support tech for BarTender and they do not have any answers so I wanted to see if anyone has ran into this problem and if anyone has a suggestion as to how to fix this problem.  Any information would be greatly appreciated.

All Replies
  • I have used Bartender to query MAS data many times. Can you please detail which tables you are tying to read. Also did you create a new silent DSN for BarTender to use? One thing I have also done is to create a MS Access database with SQL Specific Pass Through Queries  and have BarTender use that as a data source as this method bypasses many layers of the ODBC driver and returns data faster and with less errors.

  • I was using PO Receipt Header/ Detail & CI Item.  I did not create a new DSN for the BarTender .  Did you just connect Access to MAS thru the ODBC then connect BarTender thru Access?  

  • The problem with using the SOTAMAS90 DSN is that you have to log in with each connection. When you create another DSN and include the company, user ID and password you are not prompted for a log in.  And yes I connected Access to MAS through the SOTAMAS90 DSN but I used a SQL Specific Pass Through Query which allows me to code in the log in so I am not prompted.  A query was created for each table.  I then connected BarTender to the Access database.