Visual Basic Syntax - Print Job Stuck in Spool - Sometimes

Author

Print Job Stuck in Spool - Sometimes - Help!

John Kotuby

2005-03-02, 4:07 pm

Hi Guys,

I sure hope an MS VIP 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 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! 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 selcted 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.

Thanks in advance for any help

John Kotuby

Bob O`Bob

2005-03-02, 4:07 pm

John Kotuby wrote:

> 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! 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.

Just a guess...
Is this printer shared over the network?
Even though it's physically local, is it installed as a network printer?
And if so - is it really necessary?

I can't imagine WHY such things should matter, but I'd certainly
investigate them anyway if such a problem were dropped in my lap.

Bob

John Kotuby

2005-03-02, 4:07 pm

Hi Bob,

I recognize you from a discussion I initiated back in December regarding VB
being a memory hog and how to mitigate that problem. How are you? and thanks
for the input.

About an hour ago I logged into the workstation that is being used for the
check printing and looked at the printer properties. It is set to "Not
Shared".

"Bob O`Bob" <filterbob@yahoogroups.com> wrote in message
news:%23x5u0p1HFHA.2276@TK2MSFTNGP15.phx.gbl...
> John Kotuby wrote:
>
>
>
> Just a guess...
> Is this printer shared over the network?
> Even though it's physically local, is it installed as a network printer?
> And if so - is it really necessary?
>
> I can't imagine WHY such things should matter, but I'd certainly
> investigate them anyway if such a problem were dropped in my lap.
>
>
> Bob

Sponsored Links