>Thanks for the replay Al. We already have all the tables on the servers. It's the FPW 2.6 program itself that I'm talking about, not the generated .APP/.EXE. My memory told me there was a big difference (faster) having FPW 2.6 local. Am I suffering Alzheimer's already?

That should definitely be local - that's being used all the time (no matter if you're talking of the foxw.exe or the *.eso files). Though, the same thing applies: it just loads slower from the network, but once it's loaded it stays in memory and doesn't have to reload.

One thing which did help in some DOS networks in the past - mark as many common files as read only as you can. The executable, the libraries, whatever you don't update during a run. Some networks really love it, because the whole locking scheme doesn't apply anymore, and you are relieved of lots of overhead.