>>>About 2 months ago, this client was hit by a severe virus and had to replace all programs.
>>>Fortunately the network people had good backups and utilities and the client was back up and running in a few hours.
>>>
>>>Since then - I'm not sure there is a connection with that event - one report that has been running OK for years prints a few pages and then, when a group changes, pauses for about 5 minutes before printing the next group's data, and repeats that pattern for all groups.
>>>
>>>The process used to take a few minutes, now it takes almost an hour.
>>>
>>>The app uses an exe that I create and upload. The report forms are not in the .exe.
>>>
>>>I'm suspecting the VFP dll that they restored, but that's just speculation.
>>>
>>>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?