[[Thanks Dorris]]
For those just reading this, I'm taking the thread away from her since it was my problem that she posted for me.
-------------
Let me preface all this with the following: I can get the code to work just fine! Works Great! Slick as...well...enough of that. Anyway, to answer your question regarding errors; I get an OLE exception code "...no printer called [blah]". I've also tried a variation to the code, but I get "Print Processor is Unknown". All of these go away if I just define the printer and install the print drivers first.

The PROBLEM occurs when you introduce the user (ain't it always the case).
To make all this work under XP (btw: attaching to multiple print queues across NOVELL Networks.) I've had to set up each of the printers so that the drivers were installed on the user's machine.

The user, however, does not want ANY reference to the queues, printers, etc to exist on the machines! This is for a security related issue but it's not a major one. They don't want users "accidently" selecting these printers for other printjobs since they hold special paper.

The FOXDOS application that we are replacing used an old NPRINT type library that supported CAPTURE etc. The app would pull a queue from a user's preference table and connection "on-the-fly" to print something. The old application won't run under XP. Best as I can tell, it's because it demands to know what printer-type is at the other end of the queue path. And this is what is causing the problems. The user doesn't want to know, and XP demands to know.

Anyway, I've tried going around all the printers, queues, clients, networks, etc by replacing their old 16-bit library with WSCRIPT but I can't get it to work with an "unknown" printer-queue. Again, the drivers seem to be required.

Thanks
--Don