Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Pages ejecting instead of printing...help
Message
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Miscellaneous
Thread ID:
00325878
Message ID:
00325991
Views:
22
>I'm following you, the printer controls specified by the report (the report memo .frt) are for the inkjet...but how do I set the printer for the report at run time? I use the the command: SET PRINTER TO NAME GETPRINTER(). Shouldn't that override the printer controls specified in the report memo? Or, how do I setup the report so it's printer independent?

Wipe out the printer information in the .FRX's EXPR and TAG fields related to the printer - I believe there is an entry in the FAQ describing how to do this either at runtime or just before compiling into an .EXE. Look at the following entries in the FAQ:

527 My SET PRINTER TO NAME... won't work, why? 05/24/1999
528 SET PRINTER still doesn't work? 05/26/1999
552 Why won't my report print to the SET PRINTER TO NAME printer? 07/29/1999


>Thanks,
>Allen
>
>>>Hi,
>>>I am trying to run a report on an Epson LQ-570+ dot matrix printer but instead all I get are page feeds (aka. form feeds).
>>>However, this report prints fine using my Epson Inkjet printer. I tried switching between the Windows driver and the driver Epson provides, but I get the same results. Yet, I can print out of this same dot matrix printer in other application (ie. Word and Test Print in Printer setup) just fine.
>>
>>The control sequences are not identical, so if your output is producing suff formatted for the InkJet, the DMP is not going to recognize the print codes, especially if it's sending graphics sequences.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform