lemonjuice,
Hm. I don't recall ever seeing this type of behavior.
About the only things I can think of are to:
1. Verify that you're using the latest printer driver available for your printer. Check the vendors website and see if there's a new driver for your version of Windows. Alternatively, you might try using the universal driver from Microsoft.
2. Check the details of the printer driver and see if there are settings for converting fonts to bitmaps and the like. There were times when this would help older printers render things more correctly.
3. Try turning off the spooling. Perhaps there's simply too much information for the printer's buffer.
4. As a last report, trying using ObjectPal to print each page individually. This take a bit to pull off, but I have seen cases (again, with older versions) where this was needed, especially with complex reports.
Along the same lines as the previous, you might try making sure the report is completely rendered before printing it. To do this, you have to open the report and move to each page. This sets it up in memory and may help reduce the processing time between Paradox's report generator and the communication with the printer itself.
Before trying to complicated ObjectPal approaches, though, I'd probabyl try creating a different report and seeing if I could duplicate the behavior. Perhaps there's some combination of lines, objects, and so forth that are tripping over some glitch in the driver. It's hard to say, really.
I know this is vague, but I hope it helps at least a little...
-- Lance
