web pages !! obviously to the printer!!¡¡¡
I don't believe John was trying to be mean, just trying to be polite to
explain (without as many words), it sounds like you are trying to code
something up which decides for the user to print something out, but it's
difficult to predict "where" to print to. This comes up every once in a
while in a client/server environment. The "where" means if you want to
force the client to print something, which client printer do you (the server
code) pick? Do you use the default printer, do you give the user a choice?
Either way, you may/most likely will have security implications. If you
want to print on the server end (highly unlikely but I've seen this happen),
then you can go ahead and do it, but the client might have to wait for the
hard copy to be sent to them. :>
If you want to totally control the user experience from the server end, you
could create a client control which your server code could talk to, in which
you send that control the doc to print and it controls it. But I've seen
this suggested in the past, and it's a bit more involved than what you are
probably looking for. Mabye?
You may want to change your scenario slightly. I've seen this where the
webpage provided a Print button and you either use JS to print the current
page (make sure it fits in the margins for the default printer), or goto
another page specifically designed for printer output.
Another solution I just saw two weeks ago, is to play with CSS with a
printer section, but I'm a bit ignorant on this area. I'm sure a google
search will clear things up if this sounds like what you want.
Good luck.