Again, in our case we create a PAGEMODE report to a file and then build up a command to do a ZIP CMD /C NET USE LPT1 uncprintername then execute that command, followed by OUTPUT PRINTER, TYPE filename, OUTPUT SCREEN. (This is at odds with what I said in my original message; I did a PROPERTY programmer_brain REFRESH 'TRUE' before creating this reply ...)
I suspect the PRNSETUP would work as well, assuming the printer is set up as a printer on that PC. The nice thing about doing the NET USE is that the printer does not have to be set up on the subject PC. Only thing is afterwards you have to also do ZIP CMD /C NET USE LPT1 /D to "uncapture" the printer.
W98? Beats me ... but the NET USE approach ought to work.
Emmitt:
I like this idea. I assume you grab the printer from the table and then do
a PRNSETUP &vprinter? It looks like from your syntext that it's probably
an XP workstation environment because you're using the UNC. If I have a
mixture of XP and Win98, will the Win98 print using the UNC? Or maybe I
would need 2 columns -- one with the XP UNC name and one with the
regular Win98 printer name -- and pick the one based on their OS.
Karen
We run a month-end closing process that generates many, many reports. These reports get printed all over our wide area network. We have a table that associates a report name with a printer UNC (\\servername\printername). As the report is generated, we look up the printer it goes to and send the report there.
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT 06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]
