J
John Kotuby
Hi Guys,
I sure hope an MS MVP is available for this one!
I am not sure if this belongs in the VB group or if the problem is related
to XP. I posted this in the VB.SYNTAX group but got only one reply that was
more of a question than an answer?
I have a VB program (VB6 SP6) distributed to 30 customers. Within the
program is a Check Printing module that allows approval and printing of
disbursement checks to suppliers.
I use the Printer object, cycle through all the checks (anywhere from 1 to
100 or more) and then issue Printer.EndDoc. It is working beautifully at all
sites except one. For this one user who prints all the checks for their
office, when a run is more than about 25 checks the job seems to get stuck
in the Spool. She has been closing the VB program, logging out of the
network, and then logging back on to get the job to reach the printer. NOTE:
The printer is attached directly to her LPT1 port and it is NOT shared! When
she logs back on to
the network, ALL the checks print nice as pie. This user, at my request,
yesterday printed a 50 page Word document to the same printer from the same
workstation with no problem. So now I am on the hotseat to find a solution.
A number of the other sites regularly print more than 25 checks in a run and
do not report this problem (yet).
I call the Common Dialog control to direct the output to the selected
printer (in the problem case it is always the same printer that is used).
However, I do not pull any properties of the selected printer into the
Printer object after the selection of printer. Like I said, it is working
fine everywhere else. And it is working fine at the problem site until a
certain number of checks is reached in the run, about 25.
I thought about issuing a Printer.EndDoc after each individual check, but I
am afraid of causing breakage, because the program is released to so many
sites where it is working just fine.
The user with the problem is running a Windows XP machine. When I look at
the System Properties , it does not look like XP has had ANY service packs
applied. Could that possibly be a cause for print spooling difficulties?
Thanks in advance for any help
John Kotuby
I sure hope an MS MVP is available for this one!
I am not sure if this belongs in the VB group or if the problem is related
to XP. I posted this in the VB.SYNTAX group but got only one reply that was
more of a question than an answer?
I have a VB program (VB6 SP6) distributed to 30 customers. Within the
program is a Check Printing module that allows approval and printing of
disbursement checks to suppliers.
I use the Printer object, cycle through all the checks (anywhere from 1 to
100 or more) and then issue Printer.EndDoc. It is working beautifully at all
sites except one. For this one user who prints all the checks for their
office, when a run is more than about 25 checks the job seems to get stuck
in the Spool. She has been closing the VB program, logging out of the
network, and then logging back on to get the job to reach the printer. NOTE:
The printer is attached directly to her LPT1 port and it is NOT shared! When
she logs back on to
the network, ALL the checks print nice as pie. This user, at my request,
yesterday printed a 50 page Word document to the same printer from the same
workstation with no problem. So now I am on the hotseat to find a solution.
A number of the other sites regularly print more than 25 checks in a run and
do not report this problem (yet).
I call the Common Dialog control to direct the output to the selected
printer (in the problem case it is always the same printer that is used).
However, I do not pull any properties of the selected printer into the
Printer object after the selection of printer. Like I said, it is working
fine everywhere else. And it is working fine at the problem site until a
certain number of checks is reached in the run, about 25.
I thought about issuing a Printer.EndDoc after each individual check, but I
am afraid of causing breakage, because the program is released to so many
sites where it is working just fine.
The user with the problem is running a Windows XP machine. When I look at
the System Properties , it does not look like XP has had ANY service packs
applied. Could that possibly be a cause for print spooling difficulties?
Thanks in advance for any help
John Kotuby