|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
To: sapr3-soft@MIT.EDU Date: 13 Sep 1999 08:19:19 -0500 From: popey@cix.compulink.co.uk (by way of SAP Moderator <popey@cix.compulink.co.uk>) Message-Id: <7ritkn$a7i@nexus.netconcepts.com> If anyone prints to that output device within R/3, the job will come back over the network to *their* PC. It will be handed to whichever printer is defined within windows as the default printer. You can also specify a device type of "SAPWIN" which will hand the job to the windows spooler in a "raw" format that the windows spooler can then convert (via the local printer driver) before sending on to the printer. Especially useful if you have a jumble of printers of different types/manufacturers etc. WARNING! Major problem with this type of device type is that it doesn't use the spool work process to send the output request to the users PC. A dialog work process is used. Hence if a lot of people are using the output device to print to their local printer, then you will tie up a number of dialog work processes - which is only a bad thing! Second WARNING! if users have their windows default printer set to a networked printer somewhere on the LAN then the job will come over the network to their PC - and then be forwarded by windows back over the network to the printer/printserver. Double traffic. Hope that helps. Al. http://www.popey.com/
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |