Can't Pass Query To Bartender? Follow

0
Avatar
Legacy Poster

Hello,

We have Commander installed correctly, and if we do a simple trigger file and print a basic label it works.

However, if we try to pass a parameter it is not working...

/AF="D:\Program Files\Seagull\Bartender Labels\<hidden company name>\<hidden name>\(AS) - Auto Skids.btw" /P /D="%Trigger File Name%" /DD /Close /?Packing Slip #=<Trigger Contents>

Bartender's logging shows the packing slip that is in the trigger file (e.g. 71762) and is passing it along fine:

/AF="D:\Program Files\Seagull\Bartender Labels\<hidden company name>\<hidden name>\(AS) - Auto Skids.btw" /P /D="%Trigger File Name%" /DD /Close /?Packing Slip #=71762

We have a simple 'Bartender' command type listening for a simple text file with a 5 digit packing slip number in it. Bartender just won't print the label... any ideas? As I said, it works with everything else but sending along a query response won't work. Could it be the space and pound sign in the /? argument??

7 comments

0
Avatar
Domingo Rodriguez
Moderator
Comment actions Permalink

Hello Jesh,

It looks like you will need to create a query prompt without spaces in it. (E.g. PackingSlip#). The following trigger file printed the correct label for me:

%BTW% /AF="C:\Users\drodriguez\Desktop\Issue 08-10\New Commander Test\Document.btw" /P /?PackingSlip#="71762"
%END%

Also, for testing purposes, you can switch Commander to run as an application (rather than as a service) via the "Administer > Service Setup" Menu entry. Now, after starting detection but before sending the trigger file, choose the "Detection > Show All Running BarTender" Menu entry. This will make visible the underlying BarTender process. You can now send the trigger file, switch to BarTender and check what happens in BarTender (if the label format opens, if an error message appears...).

If you would still have problems, please contact Seagull technical support either via telephone or email.
0
Avatar
Legacy Poster
Comment actions Permalink

Domingo,

Currently we have it set up as Command Type: Bartender, Command: /AF="D:\Program Files\Seagull\Bartender Labels\SMT\Caterpillar\(AS) - Auto Skids.btw" /P /D="%Trigger File Name%" /?PackingSlip#=<Trigger Contents>

The Trigger file is packnum.dd and the contents of this text file ONLY says 71672 (or whatever number).'

The Logging is showing everything fine, but no printing. Should I try a commander script? Maybe that is the issue?
0
Avatar
Legacy Poster
Comment actions Permalink

Nevermind, I tried it as a command script and nothing.
0
Avatar
Legacy Poster
Comment actions Permalink

Problem fixed. It is not liking the /D="%Trigger File Name%" argument. Any ideas why?
0
Avatar
Domingo Rodriguez
Moderator
Comment actions Permalink

Jesh,

Could you paste the entire trigger file content in a new post? The /D="%Trigger File Name%" parameter is only used when / if you're also going to supply variable data inside the trigger file (apart from the query prompt value). Is that the case?
0
Avatar
Legacy Poster
Comment actions Permalink

[quote name='Domingo - Seagull Support' timestamp='1349707725' post='3432']
Jesh,

Could you paste the entire trigger file content in a new post? The /D="%Trigger File Name%" parameter is only used when / if you're also going to supply variable data inside the trigger file (apart from the query prompt value). Is that the case?
[/quote]

Domingo this issue has been resolved. It looks like there were other underlying issues that were cleared up. Looks like the vb.net was creating the file with empty data, then writing the data in it. Sometimes bartender would get the file with the data, sometimes no data.

Thank you for your help,

Greg
0
Avatar
Domingo Rodriguez
Moderator
Comment actions Permalink

Thanks Greg.

It would be fine if you paste the entire content of the trigger file to this topic, as this might help others trying to also supply query prompt values at print time using Commander.

Please sign in to leave a comment.