[THIN] Re: Question about printers in 2003
- From: Jason Patten <pattenj@xxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Mon, 26 Jul 2004 12:59:23 -0400
I could do that for the check printers, just make sure to set permissions
or groups up to only allow the authorized users. That could work.
Jason
-----Original Message-----
From: Jim Kenzig http://thin.net [mailto:jimkenz@xxxxxxxxxxxxxx]
Sent: Monday, July 26, 2004 12:12 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Question about printers in 2003
Sure don't use autocreated printers. Set up static printers for the
workstations on your servers.
JK
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf
Of Jason Patten
Sent: Monday, July 26, 2004 12:04 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Question about printers in 2003
We have an application that does check printing. The check printing module
"locks" in the printer name for use in the module. However in 2003 the
session ID changes each time the person logs in and this changes the
identification of the printer. Is there a way to ensure a user gets the
same Session ID every time, or alternatively drop the session ID from the
printer identification?
Jason
670,616,629 mph. Its not just a good idea, its the law.
Other related posts:
