![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
#12
| |||
| |||
|
|
That code doesn't seem to be resetting the default printer correctly or I'm using it wrong. Looking at: http://allenbrowne.com/AppPrintMgtCode.html I use this code when db is opened. : Set Application.Printer = Application.Printers("Microsoft XPS Document Writer") No api or extra code module and the default printer stays the same after the user exits the application. Should I be surprised this hasn't been fixed since 2003 or more surprised there aren't any others in a network printer environment coming up against this problem regularly? Anyway big thanks to Tony and Allen! Another strange thing about this though - I've set up 2003 mdb databases here too and never ran into this problem. |
#13
| |||
| |||
|
|
The network printer has been a Windows problem for a very long time. I remember seeing it on Windows 98 looking at printers on a Novel 3.x server. It was always workstation specific. Note: you may want to verify your network connection, unstable connections can cause a timeout when communicating with the printer. |
#14
| |||
| |||
|
|
The network printer has been a Windows problem for a very long time. I remember seeing it on Windows 98 looking at printers on a Novel 3.x server. It was always workstation specific. Note: you may want to verify your network connection, unstable connections can cause a timeout when communicating with the printer. This is WinXP with Novell iPrint Client v04.26.00. I'm not a network guy, don't even have admin account on this computer. How would I tell them their network has a problem when everyone else can print documents? Sure, my network connection is sometimes intolerably slow but sometimes it's fast as anything. In other words, when I call the help desk and tell them their workstation has a problem - will they just be able to come over, test and repair it or will they even be able to detect it? Thanks |
![]() |
| Thread Tools | |
| Display Modes | |
| |