While at same client with the ODBC problem (not a good
day) had a strange printing problem.  A program does a
cursor and prints a report one at a time by client (RBWin
6.5++).  The report can ONLY be printed to her local printer
because we get a memory overflow when printing to the
networked printer (traced to an Okidata not being totally
compatible with a JetDirect card).  Anyway, printing to her
local printer has been working beautifully for months.

Yesterday she got a memory overflow problem on that local
printer after printing just one report.  We put a similar
printer on her local port, and got a memory overflow on
that printer too.  We did a complete cold boot, made sure
no other programs were open. 

Then we took that local printer and attached it locally to a
laptop on the network, and it works just fine, so it isn't
the printer I assume.  So some detective work here -- what
could be wrong that we could check for?  The client uses
her workstation for Internet access and is always
downloading and installing little utilities, like new screen
savers and a date/time calendar on the task bar. 

Would appreciate any clues...


Karen

Reply via email to