Bartender: Error Message #3226 & #6670
On two different machines, I am attempting to print a label using the same excel database. The label and Excel files are in the same shared directory. I am able to open the spreadhseet directly from either machine and the bartender label (btw) file from either machine.
One machine, I have no problem. I could open the btw file and print the label using either xls or xlsx file as the database source.
However, the second machine - I can open the label, but when I attempt to print a label, it prompts correctly for the data required, but then I got the Error Message #6670. I created a brand new xls file by copying and pasting the data from the original spreadsheet as was recommended on one forum, but still, I cannot print the label.
I then tried to login to the second machine using my credentials (full access to everything) to and I get the same results EXCEPT I get Error Message #3226.
Does anybody have any ideas?
-
This is a limitation of Excel I'm afraid. Excel uses exclusive file locking, meaning that only one application/computer can connect to it at any one time. I suggest that you use a proper database instead of Excel for more sophisticated record level locking and access types.
0 -
I've connected my Labels to an Access database and get the same problem Error #6670. I can open the label and get to the data prompt but in comes up with the error after you have entered the data. So basically, if you connect to your data source directly, you get one error, and if you connect to the same data source via access (as suggested in various posts), you get another....
0 -
John,
What Edition, Version and Build of BarTender is in use?
What Windows Version and Service Pack?
Could you attach a screenshot of the error messages you get in BarTender.
If this same problem is reported in a different post, please send me a link to this post.
0 -
This is a limitation of Excel I'm afraid. Excel uses exclusive file locking, meaning that only one application/computer can connect to it at any one time. I suggest that you use a proper database instead of Excel for more sophisticated record level locking and access types.
BarTender appears to lock Excel only while it is actually quereing for data. Once it's done (a second or 2 usually), it becomes available again. We use it in a production environment with multiple stations accessing the DB. We also use an Oracle DB for some stations, but both Excel and Oracle have their own drawbacks. Our problems with Oracle are only due to our Oracle client, which is massively cumbersome.
Most likely the problem the OP has is with OLE DB network access driver compatability. We are tracking down the same error. Many machines on our network can access an Excel file, but one new one cannont (all versions of all software the same: Excel 2013, BarTender 9.4 SP3, Windows 7).
If we find anything I'll post back.
0 -
DieselOx,
Excel can make use of two database drivers: Jet OLE DB et ACE.OLEDB. Please check and make sure that when you connect to the database using OLE DB that the same driver is being used at all computers. You could even connect to the Excel spreadsheet using a "General OLE DB Provider" in BarTender's database connection setup dialog and then search to see what type of OLE DB provider for Excel you can use at the different computers.
Sometimes, it also helps to install the latest Office System Driver connectivity Components:
http://www.microsoft.com/en-us/download/confirmation.aspx?id=23734
Try as well to install the latest Access database engine redistributable:
http://www.microsoft.com/en-us/download/details.aspx?id=13255
0 -
DieselOx,
Excel can make use of two database drivers: Jet OLE DB et ACE.OLEDB. Please check and make sure that when you connect to the database using OLE DB that the same driver is being used at all computers. You could even connect to the Excel spreadsheet using a "General OLE DB Provider" in BarTender's database connection setup dialog and then search to see what type of OLE DB provider for Excel you can use at the different computers.
Sometimes, it also helps to install the latest Office System Driver connectivity Components:
http://www.microsoft.com/en-us/download/confirmation.aspx?id=23734
Try as well to install the latest Access database engine redistributable:
http://www.microsoft.com/en-us/download/details.aspx?id=13255
The second link had the drivers we need. Just now had to roll out a new system on another computer, needed to install AccessDatabaseEngine.exe (not the 64-bit choice). Our problem crops up because we are using a mix of 32-bit and 64-bit Office on a mix of 32 and 64-bit computers. 64-bit computers don't automatically install drivers for files created on 32-bit office. So I create an Excel DB on my 32-bit Office, and the newer production computer running 64-bit Office lacks the correct drivers.
This fixes it every time. Thanks.
Chris
0 -
OK, thanks for the update!
0
Iniciar sesión para dejar un comentario.
Comentarios
7 comentarios