Here is my related question, regarding performance and placement of exe

On one of the VFP listserve (or perhaps here, sorry, cant remember),
someone posted a performance problem to the effect that certain forms
were so complex that if a User simple played with the mouse absent mindedly,
moving it around the form, that network performance really degraded,
and one could see activity or workload dramatically increase on
some kind of server monitor. That thread went on to discuss NIC cards
and various network tuning options, but my first thought (out of
curiousity, because im sort of a beginner) was, WHY cant the exe,
etc. be on the workstaton client, and just have the crucial shared
tables on the server (as a way to maximize performance). The answer
that came immediatly to mind (and I am wondering if my thinking is
correct in all these matters) was that perhaps the installation has
100 workstations, and that deploying modifications, (if it is a
volatile, frequently modified application) would become a time-consuming
task..... and perhaps THIS consideration was the reason why the EXE
was placed on the server, so that changes could be deployed to
one place, and all 100 workstations would be upgraded automatically.

Question 1: Am I correct in the above assumptions.

Question 2: If I AM correct, then what are the options/trade-offs
to placing the exe on each workstation (for maximum performance)
versus placing the exe on the server (for maximum ease of
modification)? Are there any "tricks" or techniques, which would
allow someone to "have there cake and eat it", so to speak.
I think I once saw a post where, when an app was modified, some
the new exe was placed on the server, and some flag was set in some
table, which each client machine app tested upon every log-in.
If the flag indicated that the EXE had been upgraded, then
the app on the client triggered some procedure which COPIED the
new app to the client, and forced the user to log out, and log
back in. Is anyone aware of such a technique?

Thanks,

Bill Buell