>>Hi all,
>> Having a discussion on this end with no real answer. Can any one tell me if there is any advantage for working with FPW 2.6 locally as oppsed to having the program on a server. We have 5 guys currently working from a server. I remember seeing quite an improvement locally, but I have other people saying it shouldn't make a difference.
>
>If you want everyone to share the same database, the tables must reside on a server; you have no choice there. So, it looks like you're asking if there is any advantage to having the .APP/.EXE on a local HD rather than the server disk.
>
>Local disk access is faster than network (even 100BASE-T), so initial program load will be faster from a local disk. However, once loaded much or all of the program will be cached in local RAM so from that point onwards the difference will be minimal. This is especially true with modern machines that tend to have lots of RAM, and the relatively small FP 2.x apps/executables.
>
>It is much more important to make sure you set the TMPFILES setting in CONFIG.FPW to make sure it's pointing to a folder on a local disk.


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?

Pete