Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
$$$ and FOPEN('PRN') -- Sometimes they work ??
Message
From
20/06/1999 00:46:53
 
 
To
19/06/1999 23:22:51
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00231857
Message ID:
00231860
Views:
19
>When printing to a dot-matrix printer I often like to bypass the Windows printer driver. For instance I'm setting up my reservation app on some front desk computers that each have a little Okidata printer attached. When I print using SET PRINT ON, the print head makes 4 passes for each line and the result is still inferior to the standard Okidata printer font.
>
>On my development computer I can use either $$$ or FOPEN('PRN') to bypass the Windows driver. But on most of the client's computer I get the error 'Error accessing printer spooler' when I try to use $$$ to print to the local dot-matrix computer. Ironically, it seems to work if I select one of the network laser printers as default (when I don't need it).
>
>Anyone have a clue as to what affects the success of these print methods?
>
>It may be significant that my computer (where they work) is not on a network.
>
>On one computer, I was able to use ??? after reinstalling the standard Windows Okidata printer driver. But I still can't use FOPEN which I prefer.
>
>Anyway to tell in advance if $$$ is going to work?
>
>All suggestions welcome.
>

An alternative that I use - printing to a file and then sending the file directly to the port using the CopyFile() API call works uniformly across platforms; take a look at the FAQ entry I posted on the subject.
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