>I wonder if the SMB / oplocking might play a role, as early vfp was tweaked to run on SMB1. I don't remember much on networking issues with FPW - as it had no views or buffering, local caching was not so important. Dunno how a grid/browse was implemented, and if reprocess might hit vfp heavier as it "expects" local data sets.

Tamar said the production environment is running with local data and that she sees the same results running on a local workstation. If both cases are truly local storage (i.e. app on RDS is accessing data on a local drive letter) then SMB and the networking stack should not be involved at all.

OTOH I've seen old apps with hard-coded data paths that need to run on both workstation and TS/RDS servers on the same network. The workstations require a separate drive letter such as F:, which means the same app running on the RDS server needs network mapping of F: to its own local storage/share (which is certainly possible). In that case SMB and networking are involved even though the ultimate destination is local.