Thanks to both of you for your reply. I do understand that threading is not going to allow me to make my printing faster. My original problem (which I should have noted) was that one of our users wanted to manipulate the GUI while something went to the printer. The printer would just take over everything. I don't think they were able to use the GUI at all when something went to the printer before, which made me think that threading it would make their user experience better. It may still be a must have in order to allow the possibility of that occuring.
But threading didn't seem to alleviate my problem because although the user (me in this case) could manipulate the GUI somewhat, the print spooling still took almost all of the bandwidth. I would click on the "Open" icon to open a new doc in the GUI, and it would wait until at least 2 more pages had spooled (15-30 secs) before it got there. I'm sure they have a lot bigger docs than the one I'm trying to print as a test(4 page TIFF), which leads me to believe they're not going to satisfied... and I don't want that.
I'm not really sure where to go at this point. The printing call could be a little broken up maybe... I'm going to look at that. Maybe I need to try and just make the image smaller before it goes to the printer... hopefully with little loss in quality. O, the trials of a developer
Thanks again-
John
[ April 28, 2004: Message edited by: John Richardson ]