The limited information I can find suggests that I should be able to find a checkbox for ‘print local’ when attempting to output a job. In the Output Configuration window I can see that my job is set to Output Local: No, but I cannot interact with this in any way to change it.
Can anyone tell me how I change this? Thanks a lot.
The “Output Local” option forces the software to use the local Print Server (OLConnect_Server service engine on the local system) in the case where the Designer has been set to use a remote Print Server.
A remote Print Server (or OLConnect_Server service on a remote system) can be set in the Designer by clicking on the Window tab > Preferences >Print > General. Therefore, if you have another system with a licensed OLConnect Server, you may force the Designer to use that remote server to generate your output. Please note that all spool files output will be generated on the remote server file system instead unless you specify a full UNC path, which points to the local system. Using a remote Print Server can sometimes be useful to test a functionality, which may not be available on the local Print Server license. For instance, a remote Print Server license may have a PPML\VPS or AFPDS license, which may not be available on the local Print Server license.
Therefore, the “Output Local” option gives you the choice to generate output using the Local Print Server license in cases where your preferences point to a remote server. If you do not have a remote server license and you do not select this option, the software will use the local Print Server by default.
So what Rod is actually saying… If it is a PC or laptop with only Connect designer on it then you go to File-Print, select Advanced button and then select the Output Local checkbox.
Regards,
S
Thanks very much for your help, it appears my problem is connecting to the print server, as soon as I select print I get a print server error. Looks like my problem is completely different to the one I asked. Thanks a lot anyway.
Thanks for clearing this up it appears the problem is indeed print server related.