Databse workbook file path changes for all files when updating
We use Bartender in a manufacturing environment to print labels for various products. We have a couple hundred files with various labels in them for each product.
Recently, we've encountered an issue with file paths changing across the whole tree of folders. Before, each file (xxx.btw) could have its own workbook path assigned to it regardless of which file it was in. However, something changed in one file which required us to point the file to a new file path, and now every time we open another file, the workbook points to the previous file.
For example, we worked on a label that required the database 3974.xls. Then we open a different file in a different folder, and it is still looking at 3974.xls instead. If we update 4074.xls to be correct, the next file we open will be looking at 4074.xls, etc etc.
We previously had separate workbook paths for separate files. We're not sure what changed (Bartender has not been updated, nor have any drivers) but this has been causing slow downs. Does anyone have any advice on what setting may have changed, or what can be done to keep the file paths dependent on the file?
It looks like you are using a Named Database Connection, Excel File, and so when you change the configuration for that to a different file that is then changed for every label linked to the Named source.
For the label that now needs to use a different file, you need to use the Stop Using Named Connection option (#) first and then configure the setup.
# It looks like you are using an old version of BarTender and so this option may be named slightly differently and I am not sure what screen it will be on.0
I appreciate your response, Peter.
We are unfortunately using an older version of BT (6, I believe) but since this issue only started recently, I wasn't sure if it was a version issue or not. I don't think we have "Stop Using Named Connection" options. It looks like it would be in the database -> connections tab which we don't have.
Do you think using an 'alias' would help keep our databases separate?
You may need to create a new named database connection then and switch the file you want to change to that one.
I cant remember how you would do this with v6 (it must be on a very old PC as i think that was around in the noughties) , but I am guessing you may have to remove the DB and then Add a new one on to get to the screens where you can configure a new named source.0
Thanks a bundle Peter. We actually got it working (for now) thanks to your advice. Believe it or not, we're running Windows 10 and still using BT V.6 (along with horribly outdated ODBC drivers). We've been pestering upper management to give us updated software but they won't budge! >:(
I appreciate you taking time to help us.0
I am surprised V6 even works on Windows 10, but at least you are up and running again0