Hey-
We have similar issues with rendering performance in RDP sessions, and have traced it to the following:
When launching our PB 19 application over RDP,
- if the RDP session loads / maps the user's local workstations printers before our application opened ... our PB app will use the user's local workstation default printer when rendering (drawing) all datawindows ... this makes our application is very slow (glitchy, as it takes 2 to 3 seconds to just switch rows)
- if the RDP session has not finished loading / mapping the user's local workstations printers before our application opens, PB will user a server side printer as the default printer when rendering (drawing) all datawindows ... our application functions as expected.
This could be related to your issue. Our TechOps team is trying to engineer a work-around to ensure our PB application is launched with a service side default printer.
Jeff/