Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Set printer to name
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00401079
Message ID:
00401848
Views:
18
>Steve,
> Thank you for the insight and don't worry, no offense taken. In all my infinate wisdom, I once had a serial port scanner stop working and was frantically trying to figure out why when someone suggested checking to make sure that the serial cable was properly connected. Imaging my suprise when doing just that solved the problem!
>
> At any rate, we have tried rebooting the machine, but it didn't seem to solve the problem. We have found that the command REPORT FORM ... TO PRINTER PROMPT does properly work, but issuing the commands SET PRINTER TO NAME ... followed by REPORT FORM ... TO PRINTER always causes the problem. If we issue SET PRINTER TO NAME ... followed by REPORT FORM ... TO PRINTER PREVIEW does work! I have no idea what the problem is, but I think I am about ready for a career change! Mabey a stock broker...
>
>
>Sincerely,
>Justin

Justin,

I'm in the same dilemma with NT vs 95/98 and was hoping to find a solution here too... What I have found is that NT supports the NAME clause, but 95 and 98 DO NOT...

Also, when trying to get a list of valid printers by using the APrinters() function, NT and 95/98 return the results in a different sequents.
Ex: Under NT,
APRINTERS( laMyPrinters ) would return
laMyPrinters[1,1] = "\\MyNTServer\MyNetworkPrinterShare"
laMyPrinters[1,2] = "MyHP_Printer1"
laMyPrinters[1,1] = "\\MyNTServer\MyOtherNetworkPrinterShare"
laMyPrinters[1,2] = "MyOther_Printer2"

But under 95/98
APRINTERS( laMyPrinters ) would return
laMyPrinters[1,1] = "MyHP_Printer1"
laMyPrinters[1,2] = "\\MyNTServer\MyNetworkPrinterShare"
laMyPrinters[1,1] = "MyOther_Printer2"
laMyPrinters[1,2] = "\\MyNTServer\MyOtherNetworkPrinterShare"

notice the UNC is listed first under NT, but second under 95/98.

From what I have found this far, it has to do with Windows interpretation of which printer is attached and available by exact name. Even though you may have a network printer installed, it will send the printjob to the network, not through your own Windows printer drivers on your pc. However, with set printer to, it appears to try using your local Windows printer drivers, doesn't find them and chokes.

Hope this helps, and if you find something more on this, please pass it back to me.

Don
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform