>>>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?
>>
>>Questions:
>>
>>1) desktop or remote desktop/citrix, etc.?
>>2) If rdp/ica, real or virtual machine?
>>3) any new anti-virus?
>>
>>I would run the report while looking at Task Manager, seeing which processes are working. If it's real-time anti-virus, this will often show that it's working hard.
>>
>>I don't know the report engine well enough to know whether it does a pass for each group before it actually prints, but I'm guessing it does in order to make possible "% of" group information. That would entail possibly writing to a tmp file. Which is where the anti-virus might be at work. Just guessing here.
>>
>>Hank
>
>It's rdp and a vm.
>The tech took another look and is convinced that it's in the local environment.

If print to PDF...Print the PDF worked at normal speed, that implies a problem with the printer or communications with it.

Is the printer attached to the remote, or the host?

By default, an RDP session prints to the default printer at the remote. Does that default printer exist and is on-line?

Some versions of RDP remote printing require that the same printer driver be installed on the host as well as the remote, even if printing is to the remote. Has this been checked? If one is 32-bit and the other 64-bit, that can be a problem as well.

Some printer settings worth checking:

- If the target printer is shared, there is a check box on the Sharing tab "Render print jobs on client computers". It's probably checked/enabled by default, it may need to be adjusted in an RDP environment
- Advanced...Print Processor should be winprint/RAW, if there's a mismatch between the remote and host it can cause problems
- Some printers install their own custom print monitors, some of which are notoriously buggy/flaky
- Many printers these days (e.g. MFP devices) are actually embedded/Linux computers. Like many other computers they may benefit from the occasional reboot. If it's an advanced workgroup machine it may have an internal hard drive which may be getting full

It's possible to manually set up convoluted printer redirection that doesn't work as intended. For example, if the user actually wants to print at the host, rather than simply disabling the default printer redirection, manual misconfiguration can cause a print job to go across the wire to the remote, then be bounced back to the host

What's the connection between the remote and host - LAN or WAN (speed?), wired or wireless?

How large is the report - lots of pages, significant graphics/images per page?