Commander Service No Print Dialogue Follow

0
Avatar
Legacy Poster

I know that you cannot show the print dialogue box when running Commander as a service. But I have issues with running Commander as an application (doesn't automatically start back up after reboot or logout and hangs).

 

Is there any other suggestions on how we can select which printer we want to send the data to. And also keep in mind we are taking information from a system that will only input the printable information we need, we cannot use the database output to include the printer information, so we either need to include VB scripting in the file to allow for a prompt screen or some other way to trick the system.

 

Any suggestions please.

3 comments

0
Avatar
Domingo Rodriguez
Moderator
Comment actions Permalink

What BT edition, version and build is in use?

 

What Windows version and service pack is in use?

 

From your post I'm not sure if when Commander runs as an application you're showing BT dialogs or not. Can you clarify please?

 

When running Commander as an application, there won't be an automatic restart of Commander after the computer reboots (this only happens when Commander runs as a service). The restriction of not allowing interactive dialogs while running Commander as a service is actually a Windows restriction, as they discovered that this is a potencial security hole due to the possible use of accounts with elevated permissions to run as a service.

 

If the ERP system isn't capable of including the printer information in the trigger file, you will need to select it at print time via the "Print" dialog (or alternatively write a front-end application which controls BarTender in the background using the .NET SDKs which would then offer the printer selection).

0
Avatar
Legacy Poster
Comment actions Permalink

What BT edition, version and build is in use?

 

What Windows version and service pack is in use?

 

From your post I'm not sure if when Commander runs as an application you're showing BT dialogs or not. Can you clarify please?

 

When running Commander as an application, there won't be an automatic restart of Commander after the computer reboots (this only happens when Commander runs as a service). The restriction of not allowing interactive dialogs while running Commander as a service is actually a Windows restriction, as they discovered that this is a potencial security hole due to the possible use of accounts with elevated permissions to run as a service.

 

If the ERP system isn't capable of including the printer information in the trigger file, you will need to select it at print time via the "Print" dialog (or alternatively write a front-end application which controls BarTender in the background using the .NET SDKs which would then offer the printer selection).

 

BT edition is Automation V10 running on Windows 7 OS

 

We are trying to use Commander to automatically print the file, the problem is that they want to be able to send it to different printers. And yes I do understand that the issues behind the print dialogue screen not coming up is a Windows problem, what I'm trying to work out is if there is any other way of having that dialogue box come up. If we run a seperate program then we remove the automation of the commander that we are looking for, we want a file to automatically printed from there program as soon as they are created but we want the option of selecting where that job is being sent.

 

And I also know that yes when Commander runs as a program the print dialogue box can come up, and yes I do know that when you reboot the computer that Commander does not start up automatically and also doesn't run properly silently in the background. These are all issues that I am aware of, I just need help with another way we can get a print dialogue box coming up or some form of selection for printers say in a print-time prompt or something.

0
Avatar
Canguita
Comment actions Permalink

Hello,

 

Please note that Commander is an application designed to automate the printing, so print dialogues cannot be displayed.

 

If you want to select different printers printing from Commander you will need to use Commander script in your trigger file.

 

Have you considered to integrate BarTender with an external application?

 

http://www.bartenderbarcodesoftware.com/label-software/whitepapers/barcode-and-label-software-integration-methods(english).pdf

 

Thanks,

 

Carlos

Please sign in to leave a comment.