>I'm mostly replying regarding the notion of putting the EXE on each workstation:
>
>I'm not a big believer of that. Although, I don't know for sure, but I would expect much if not most of the EXE gets sucked into memory at the git-go.

Nope. Lots of people believe that myth. VFP exe is not a normal exe. I used filemon and proved that the only thing that is sucked into memory is the called for part of the exe. If you have a form called JeffLeason inside the exe, when your code says DO FORM JeffLeason, filemon shows that JeffLeason.scx is "extracted" from the exe. Not just at the git-go, but every time the DO FORM JeffLeason command executes. I put the exe on local pc's at a place with 1Gb network and we saw a definite gain. We measured it at 25-30% faster. Don't forget the speed of most hard drive controllers far exceed the network card. Anything local will be fast.

>
>Also, what speed is your network? Ours is 1000 mbit and maybe yours is only 100 mbit and not any slower.
>
>I think the biggest slowdown is unoptimized queries. That said, you might not be able to optimize everything in the app and you might be stuck with some slow performance as the DBFs get large.

That's true, but again, the exe and the continual "extraction" and execution of components is a lot of wasted network traffic.