![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi - We have a FPW 2.6 application. When a customer decides to change to a new printer, I know we will be getting some support calls. Invariably the system would not print to the new printer. It will just sit there. ... no error messages ... nothing. Most of the time we have solved this problem by modifying the printer property to bypass the spooling and 'print directly to printer'. This works. I fail to understand what is going on. Any ideas? Another question, is there anything we can do at the application level so that we dont get this support calls...? Thanks in advance... Shah |
#3
| |||
| |||
|
|
Hi - We have a FPW 2.6 application. When a customer decides to change to a new printer, I know we will be getting some support calls. Invariably the system would not print to the new printer. It will just sit there. ... no error messages ... nothing. Most of the time we have solved this problem by modifying the printer property to bypass the spooling and 'print directly to printer'. This works. I fail to understand what is going on. Any ideas? Another question, is there anything we can do at the application level so that we dont get this support calls...? Thanks in advance... Shah |
#4
| |||
| |||
|
|
Hi - We have a FPW 2.6 application. When a customer decides to change to a new printer, I know we will be getting some support calls. Invariably the system would not print to the new printer. It will just sit there. ... no error messages ... nothing. Most of the time we have solved this problem by modifying the printer property to bypass the spooling and 'print directly to printer'. This works. I fail to understand what is going on. Any ideas? Another question, is there anything we can do at the application level so that we dont get this support calls...? Thanks in advance... Shah |

![]() |
| Thread Tools | |
| Display Modes | |
| |