Rich,
We had the same problem (with a different HP printer) last year. The solution turned out to have two parts: First we replaced the driver that came with the printer with one from MS (see George Tasker's comments on this) and second we had a field which exactly overlapped another (one or the other was printed depending on the WHEN clause). We had to remove these two fields and replace them with fields a couple of pixels apart. We haven't had a problem with the report since.

All this sounds more like magic than science, doesn't it?

HTH
Barbara


>A few months ago, I posted a note about a VFP6 report I created that caused the NT4 workstation
>it runs on to hang, requiring a cold reboot. The visual indication shows the print page counter dialog
>box stopping, and then the workstation just freezes. This report is a 1,400 page daily report that is critical
>to my end users. It is run from a small .PRG (that is, NOT an .exe), contains a small (less than 5K) .gif
>of our corporate logo, and creates a print data stream of about 18 Mb. There is nothing really tricky here-
>just a simple REPORT FORM... TO PRINT, a few .DBFs on an NT Server, and a few relations set. I
>suspected a hardware issue, and did the following:
>
>1. had the w/s RAM increased from 64 mb to 128 mb.
>2. increased the HP LaserJet 8100N's RAM from 16 mb to 48 mb.
>3. broke up the REPORT using the RANGE option (i.e., pages 1-250, then 251-500, 501-750, etc)
>
>Does anyone have any other suggestions, or experience with a large VFP report such as this? Is this just
>a "the VFP report writer is lousy; go with Crystal Reports...." matter??
>
>Thanks.... Rich Lieblich