>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??
>
Rich,

This sounds like a printer driver problem. HP's drivers are notorious (especially in the Fox community) for not adhering to the Microsoft Driver specifications. Try using an MS supplied driver and see if that fixes it. Even if it doesn't, this doesn't sound like a Fox problem. All VFP does is hand the print job off to winspool.drv for processing. So if you've gotten the printing dialog, this has already been done, and the problem should be between Windows and the printer.