Oh yeah, it is using Printer Objects--I just looked at the attachment. What machine was used to develop this; what are its defined printers in its Windows Print Manager? It's possible that the Printer Object used the driver on that machine and it probably doesn't match the one in NY. It can be a tricky gotcha.
[ QUOTE ]
I assume that it was printing before without a problem and now has a problem. Or is this the first time printing to NY?
Two things to review are the connection itself and the print driver in New York. In the case of the WAN there might be a bandwidth issue. Just as likely is the print driver. Sometimes with newer model printers the PCL6 driver is not as stable as the PCL5e driver. This is rarely the case though. It might be that driver installed is for W2K when it needs to be the NT version of the driver.
Are FormScape Printer objects or Dynamic Printer objects being used? If Dynamic Printer, then it is better to define the printers first to be installed to the same server that hosts FormScape. In fact, that is FormScape recommended way for all printer definitions. The printer definitions won't need to be shared and naming them with a '$' appended makes these invisible to users on the network. Thus avoiding assignments conflicts. Downside is duplicate maintenance in order to stay synchronized.
[/ QUOTE ]