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.
Now, in our case, this is running in 6.5++ DOS, and the reports are PAGEMODE to a text file. Then we can simply use the COPY command to send the report to the printer. However, using PRNSETUP [printeruncname] would work just as well.
And, if the printer name changes, we change one entry in one table.
A client of mine has all 98 workstations on W2K server. Running
RBWin 6.5++
They have more printers than Mrs. Paul has fish sticks (my mother's
saying). Certain forms are always loaded in certain printers, certain
trays. So my programs are loaded with statements like:
PRNSETUP 'HP Laser Sales' or PRNSETUP 'Dot Matrix consignment',
etc. Printer names are very descriptive so in case I do a regular
PRNSETUP where they can choose, the uneducated users can figure
out which printer to choose.
Now they want to start replacing some of the older computers with new
Win XP ones. We tried this is one of her new laptops and found out that,
if I'm right (that's what I want YOU to tell me), even though the descriptive
name as above may show up in the PRNSETUP box, it returns the
"Shared Name", which is a small one-word deal. And it will also put the
server on there, so picking a printer would return something like
\\servername\HPLASER.
So with literally hundreds of programs with hard coded printer destinations,
what would involve the least amount of programming to let both OSs get
along? Is anyone out there doing it?
Karen
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT 06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]
