Karen,
The problem is that the printer is being sent Windows control codes..
which most dot matrix printers run at a slower speed.  The only way to
take advantage of high speed dot matrix printers is to print from DOS..
Thus if it is that important, have your client buy the DOS version, then
create a routine to print the statements, but give it a unique
extension, like .DRD  Then in windows, associtate the .DRD extension to
always open with RBase for Dos.  From Windows you can then simply Launch
program.DRD and it will open RBDos, run your print routine using the
High speed Dos printer control codes, and then return to RBwin when
done.  This is what we do for our invoices (over 1500 a week) and it
works great.

-- Frank

-----Original Message-----
From: tellef [mailto:[EMAIL PROTECTED]]
Sent: Sunday, June 30, 2002 12:45 PM
To: All
Subject: Printing big jobs to high speed


Hello all!

A client is printing 1600 monthly statements to their customers.
They bought a 12ppm Okidata to do the printing.  In the RBWin program
I wrote, it cursors through and is printing one customer at a time.
The original thinking was that I have to do some calculations as each
client is looked at, accumulating several variables depending on
the customer's situation that are written to a file after all
the printing is done.

Running on Win98 workstations on a Win2K network, it seems the print
spooler can't keep up.  The cursor is very fast and after printing
about 400 statements we start getting Spool32 errors.  The client
knows how to modify my program to have it start printing at wherever
it left off, and she'll get maybe 300 more, then less and less.

The hardware guy says the driver is right, installed brand new when
the printer was brought in.  She bumped up the printer memory to the
max.  I told her I could put a 'pause for <xxxx>' every 300 statements
or so to see if that helps if we could determine how long to wait for
it.  

My other thought -- if the spooler/printer can't handle 1600 individual
print jobs, would it be able to handle a 1600-page single job better?
I could change the the program to do all my calculations first, then
have the report just break on the CustID.  Printing to a file is not
an option because we need to retain formatting.


Karen
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to