Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!cernvax!chx400!ugun2b!ugsc2a!fisher
From: fisher@sc2a.unige.ch (Markus Fischer)
Newsgroups: comp.os.msdos.apps
Subject: Re: Looking for help with dBASE overflowing the print buffer
Message-ID: <272@sc2a.unige.ch>
Date: 18 Oct 90 13:49:37 GMT
References: <4d6f1a08.20b6d@apollo.HP.COM>
Organization: University of Geneva, Switzerland
Lines: 20

In article <4d6f1a08.20b6d@apollo.HP.COM>, miller_h@apollo.HP.COM (Herbert Miller) writes:
> I use dBASE IV with a Laserjet IIP w/2Meg.  When I print large reports,
> dBASE gets way ahead 
> of the printer and tries to tell me that the I have a printer error. 
> The real problem is just that the print buffer
> is full.  I'm getting really sick of waiting for a few pages to print,
> telling dBASE to retry, having it timeout, wait some more, etc.
> [...]

I had the same problem back with dBASE III (not +, mind you!).  Since that
time I've taken the habit of sending reports to disk, to be printed later.
(I need this anyways, to print accentuated chars on the HP!)

Alternatively, I load DOS' PRINT before dBASE, and do something like
 repo form ... to file.txt
 ! print file.txt

Even COPY worked better than sending a report "to print".

Markus Fischer, Dpt. of Anthropology, Geneva