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/

Thank you

another difference between the machines

the performant one is windows server 2016, the non performant one is windows 10

Thanks a lot!

Hi guys thanks for your hints but I discovered (may be) where is the point

I did a small app doing a

Retrieve

InsertRow

ScrollToRow 

On customer environement (connected with RDP) it takes more or less 4 sec

On our development enviromenet (connected with RDP) it runs immediately 

Data are more or less the same, ODBC is the same

Maybe it's a configuration of RDP?

I tried disabling clipboard and printer sharing but no way...

Thanks a lot 

I did some other tracing

the scrolltorow is slow after the insertRow..., even if i set setredraw(false) before and "true" after

Any hints?

Thanks a lot

Hi Giuseppe,

what might slow down DataWindow performance are icons (picture control and bitmap() function) and global function calls.

If your DataWindow shares data with any other DataWindow and/or DataStore, you should check these also.

Best regards,

Marc