Bartender Automation With Database Connection S’abonner

Sure you can - there's 2 patterns I can thought of:

a: Create Joined database - using SQL Inner-join like method, you can create join for multiple database. Commander replaces text database.

    See attached picture.[attachment=1343:JoinSetup.png]

b. Give query prompt value from Commander, by one field text file or Commander script.

  You can filter records using query prompt - if haven't try, check the video below 

  http://www.seagullscientific.com/label-software/training-video-(selecting-records-from-a-database-at-print-time).aspx

 This thread discussed with such setup.

 http://forums.seagullscientific.com/index.php?/topic/999-commander-trigger-file-and-bartender-template/

 See Commander white paper's example #3 for commander script.

 http://www.seagullscientific.com/label-software/whitepapers/overview-of-commander-new-201406.pdf

Hi Shotaro,

Thank you very much for your helpful information.

I was already able to make it.

Best regards,

RC

Hello Team,

I have nearly the same inquiry and unfortunately cannot solve it yet with the joined database solution. I have a trigger file containing one data set with header starting in line 3:

%BTW% /AF="C:\Label.btw" /D="%Trigger File Name%" /PRN="CAB A4+/300" /R=3 /P /DD /C=1 /CLOSE
%END%
ID;type;...

0000123456;1;...

When working only with the trigger file everything works fine. As soon as I specify a second database in the bartender template the label is not printed anymore by the commander. Quite strange is the fact, that the commander itself behaves  like the file was printed: trigger file is renamed and then deleted from the directory, which is usually only done if the file has been printed correctly.

I tried different database types (Text, Excel, Access) - none of them is working. Are there specific additional commands to be added in the trigger file if it is used with joined databases?

Best regards, Andre

Try remove /R=3 and check if that works (I know this is rather strange though - please test thoroughly).

Hi Shotaro, thanks for the fast reply. You were completely correct: As soon as I removed the "/R=3" parameter the labels are correctly printed when using a joined database. It seems that during the joining process the different rows from the trigger file (header + data)  are reduced to the data array.

Thanks a lot. Andre