>You know, if we had a Printer object the way VB does (ulp!) and not these archaic printer commands, this wouldn't be an issue. So, I suppose one solution is to write a VB DLL that exposes the properties and methods for the printer object and use that.

Been there ... Done that. I needed it a couple of years ago so that I could print graphs out of Graphics Server. It works pretty good.

-Mike