>>>>>>Any clues?
>>>>>
>>>>>These days pretty much all Windows print jobs are spooled, so once the job has been generated it should print continuously with no pauses. If you're seeing long pauses it seems to me it's likely the workstation generating the job is pausing i.e. there are delays in processing.
>>>>>
>>>>>What might cause that is likely dependent on exactly how you're generating that report. However, one thing that can slow down processing a lot is missing index tags. A while back I ran into a case where a CDX file had lost 6 of its 7 index tags, only the PK tag remained. That slowed processing down by over 100 times (i.e. speed without the tags was less than 1% of speed with the tags present).
>>>>
>>>>Thanks, Al.
>>>>
>>>>This report is driven by a cursor created by a SQL Passthrough query.
>>>>No indexes
>>>
>>>Have you verified that the temp dir cursors live in is still on the local machine and not by some fluke pointing to a network share dir?
>>
>>Will check, Thomas.
>>Viele Danke
>
>You are welcome. Come to think of (although probably not the sole culprit), let them check the # of files in vfp temp dir.
>IF this dir was included in backup, but never pruned in backup when original was cleaned, a couple of thousand old temp files might clog OS functions/actions ;-)

The tech replaced the printer driver (again) and the speed is now OK