>> A typical 32-bit Terminal Server only had ~3.2GB total memory available. If that had to support a bunch of remote users then yes, anything which could reduce session memory usage could be useful. In the modern 64-bit world I don't think VFP apps need to worry about memory usage

Thanks Al. In practice and reviewing task manager, I see no significant sys(602) memory use difference under RTS: memory use remains tiny by modern standards. FWIW, the recommendation to limit the app's foreground and background memory use to 64MB or 128MB is sometimes regarded as an error by RTS gurus, since no data-intensive app can manage on so little. ;-)

>>- It's possible SYS( 602 ) is a corner-case "trick" which RDP doesn't know about and which might interact badly with its optimizations

With SYS(602) memory rendering off, it looks as if backstyle_access is being constantly goosed in the grid, causing a distracting flicker that presumably uses heaps of bandwidth compared to a single "snap" to screen. Unless the "snap" also is being constantly goosed. I'm only testing in a local RTS environment with heaps of capacity and bandwidth, so not easy to say.

>>All that said, I think the most important thing is "YMMV". Test it for a particular remote-access environment, or offer it as a configurable preference in the app. What works great for RDP over broadband with low latency may not for GoToMyPC or Teamviewer at lower speeds over satellite.

I might mess with this a bit longer to see if I can prevent the goosing that sometimes stops after other activity. Our apps used that sys(602) setting for years by large and small sites without complaint and I wouldn't want to change it and introduce catastrophe!