>>What's available to allow one of my system's users to work from home with a copy of his VFP executable so that he can read and update the VFP file server machine on the LAN at his office ... just like he does (other than for speed) at the office?
>>
>>Bob
>
>With all the choices ... I decided to try TeamViewer just to get a reference point ... speed, ease of use etc. I picked it to experiment with because it was free as long as it was for personal use. They don't define personal vs commercial but if you aren't selling services to others through its use, I suppose it's personal.
>
>It seems to work fine. It really is a (max) 2 minute download/install per machine. fire up the downloaded startup file, choose standard or custom, and your done. The same install is needed at both host and remote. Each end gets its own numeric ID, and a numeric password (the password changes with each session start). My user can start it from his desktop on his office machine write down the ID and Password from the TeamViewer startup screen, make sure his machine isn't allowed to shift into sleep mode, and go home. He starts TeamViewer at home, then he puts in the work machine's ID and current password, and his screen then changes to show the current screen at the office. That's it. He is now the office machine's keyboard, so he can run his office machine's vfp executable, and even print reports either at home, or back on the office printer from home.
>
>The speed is great, as it's only a changing screen image, and keystrokes that get transfered. If this is all that's needed (it's all that I was looking for) then this one looks like a winner.

One thing to be wary of with TeamViewer is its philosophy is peer-to-peer rather than remote/host. That is, with it installed on both a "remote" and a "host" computer, the "host" can potentially connect to the remote as well as the remote connecting to the host. That may be desirable in some scenarios but for many it's a security risk: https://en.wikipedia.org/wiki/TeamViewer#Fraudulent_uses

It's been a couple of years since I used the product but the peer-to-peer capability used to be achieved by installing a Windows service even on the remote computer. When I last had it installed I disabled the TeamViewer service on "remote" computers to minimize these potential issues.