I can’t remember if there is any special technique required when setting..
Printer{PropPrint:Device} = ‘\\somewhere\someprinter’
I don’t have a network printer I can test with but it doesn’t appear to work at a user’s site? i.e. the saved printer is not being used the report is reverting to the default printer.
Actually, you can sorta fake a network printer.
Share a printer that’s connected to your computer.
Then you can connect to and use it as a shared printer.
Pic shows that on my computer called JX I can access and use a shared printer on that same computer.
Might tell you something.
Is the same user able to print other stuff to the network printer in question (permissions)?
Thanks Jane, that’s a good tip!
I realised that my printer is actually “on the network” it just doesn’t show with the network path in my Printers list.
I’ve had more correspondence with the customer and I’m meeting with them on Monday because I’m not really sure what their issue is except the report is reverting to the default printer instead of using the saved printer name. I thought it might be because they are using a network path “\\somepath\” but apparently that might not be the issue after all?
Unless it’s changed in Windows settings, Windows decides which printer is the default.
To get around this in a Terminal Server session I set the default printer in Windows each time a user logs in by placing a batch file in the following folder;
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp
The batch file uses;
The successful batch file that runs contains a single line;
rundll32 printui.dll,PrintUIEntry /y /n “The Printer Name Here”
It works for local and networked printers
Hope this is of some use.
cheers
Rohan
Thanks Rohan, I’ll see if I can get more details on Monday. Regards, GeoffB
