Fletcher, I have a printer class which allows you to queue up jobs to a printer but only asks for the setup at the beginning and then keeps it for subsequent reports put into the queue. That may do the job. I'll wrap it up and email you direct over the weekend and you can have a go with it.
I must admit though that I've always shyed (is that the correct spelling)?) away from duplex printing but I certainly know that all the other settings I use (page size etc.) are carried through. Dave Crozier The secret to staying young is to live honestly, eat slowly, and to lie about your age -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fletcher Johnson Sent: 21 July 2006 06:02 To: 'ProFox Email List' Subject: RE: SET PRINTER TO NAME Dave, I have a form where I have one button that says "setup printer" which calls Sys(1037). This does work to set the desired printer. But if the user selects "duplex" (double sided) printing, the printer ignores it. In this case, the program has 4 separate calls to "report form ...." so that we can generate very differently formatted portions. When I add "prompt" to the report, it doesn't remember the duplex mode either (although it will then print in duplex mode). If I set the printer as the windows default printer and then set duplex on (again as the default), it still ignores the setting. Any idea how I get ask the user once to select a printer and then have those settings preserved for each report form call after that? The prompt option currently works, but they get it four times and each time, they have to specifically set it to use duplex printing. Thanks, Fletcher -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Crozier Sent: Tuesday, July 18, 2006 2:43 AM To: 'ProFox Email List' Subject: RE: SET PRINTER TO NAME Andy, I confirm that your observations are in fact true. I always use Sys(1037) and select the "Printer" button to select the desired printer when working in a networked environment as opposed to Getprinter() as it ALWAYS sets the "VFP Printer" to the correct value. It involves users in one more "Click" to select the printer but works on all VFP versions networked or not. Dave Crozier The secret to staying young is to live honestly, eat slowly, and to lie about your age -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Davies Sent: 18 July 2006 10:31 To: [email protected] Subject: RE: SET PRINTER TO NAME Hi, I did a bit more playing with this (vfp9 ReportBehavior=80): SET PRINTER TO NAME GETPRINTER( ) *seems to work OK - but see below** ?SET("Printer",2) && Windows Default ?SET("Printer",3) && New Fox Default select foo, bah from somewhere into cursor xxx READWRITE CREATE REPORT tst FROM xxx && layout is in tag *but no printer info* (why?) REPORT FORM tst to printer && see below ** The first time I tried this I selected a printer that is no longer connected ** and the report apparently printed to the *Win* default - confirming the behaviour ** reported by Dave Crozier and others. ** I then tried Devendra's suggestion of using aprinters() and noticed that my ** selected printer was on lpt1: the same port as the Win default. ** so I tried selecting Paperport (a software printer which uses its own port) ** - this worked using the aprinters() name. I then tried ** SET PRINTER TO NAME GETPRINTER( ) again but selecting Paperport - AOK! So there seems to be no difference between getprinter and aprinters - and I offer the suggestion that the suspected bug re Win ~ Fox default printers may be a port thing - i.e. if no printer is in the frx Fox uses the printer *on the port* specified for the Fox default (I wonder which driver?) I leave more extensive testing (and networked printers) as an exercise for the reader (Dave?) <VBG> Andrew Davies MBCS CITP - AndyD 8-)# ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. Please contact [EMAIL PROTECTED] with any queries. ********************************************************************** [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
