Hi Kent,
This is a problem when Getprinter() is called.

You can provide a printer name otherwise also. Provide a combo with
installed printerlist on report screen. Populate the combo with Aprinter().
For all report get printer name from this combo value. Now you donot require
to call Getprinter(). This should work.

Bottom line is that do not call Getprinter(). Provide a printername without
a call to Getprinter().

Whenever Getprinter() is called, printer factory default setting is
obtained, not what is set in windows. I donot know this is a problem with
VFP or Windows. I think this is a problem with VFP because when a printer
dialog is called from Word/Excel, printer seting is observed, not printer
factory setting is obtained.

Devendra


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Fletcher Johnson
Sent: Tuesday, July 18, 2006 10:14 AM
To: 'ProFox Email List'
Subject: RE: SET PRINTER TO NAME


Kent,

I just ran into this same problem.  The user clicks on a button to "set up
printer" to which I then call Sys(1037).  Then they can click on print.  The
problem I have is that, even though they set the properties as desired (in
this case, duplex printing) it doesn't remember the settings.

So my users can specify all the nifty things they want, but the printer
ignores them.  I think it also goes back to the default printer thing.

I think I am stripping out the printer drivers from the .fr? Files, but I
will check.

If you find any solutions, please let me know.  And I will do the same for
you.

Take care,

Fletcher


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Kent Belan
Sent: Monday, July 17, 2006 2:45 PM
To: ProFox Email List
Subject: SET PRINTER TO NAME

Hello,

I am trying to print reports to various network printers using SET PRINTER
TO NAME (lcPrinter) where lcPrinter is loaded with a printer selected using
GETPRINTER()

Sometimes it works but 90% of the time it does not and prints to the default
printer.

The client has Windows 2000 workstations and the VFP help says this command
should work.

Anyone have an idea why this command is not working?

Thanks for your help,
Kent




[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.

Reply via email to