>>>>The entire 3MB executable is not kept in memory; the .EXE file is referenced pretty frequently, in fact.
>>>
>>>Ed,
>>>
>>>The EXE will be loaded into memory of the Win95 stations and they will take care of caching it to their local disk. There is only one reference to the the EXE on the server and that is when the EXE is initially run.
>>
>>That's not the behavior I'm seeing; each time a formset or class library is loaded for the first time, we see LAN traffic when the .EXE is located on the LAN. There are noticable differences in application performance from what I've seen.
>
>Have you tried putting the following into your config.fpw file?
>
>tmpfiles=c:\
>editwork=c:\
>sortwork=c:\
>progwork=c:\
Yep. The .EXE is still referenced for some objects embedded in the .EXE file on an as-needed basis.