>Edward,
>
>>Executable size has no impact on server because VFP actually runs it on local workstation, even if you place it on server.
>
>Actually that is not true either. Most people do not understand how VFP executables are run. To have a true understanding I'd suggest all to download filemon (www.sysinternals.com) to monitor the network traffic.
>
>
>In summary, what happens is the following.
>
>VFP executables are not regular windows executables. They consist of an header that loads and runs the support library. Then VFP starts and begins to read data from the rest of the executable. It will continue to do so for the entire duration of your application. Each time a form, classlib or even a textbox is instantiated is is going to read from the executable an thus creating network traffic. Hence the performance difference between a VFP application on a server or on a workstation. You can limit the traffic by making the executable readonly as then the parts that have been read from the executable will be cached.
>
>There are also other factors that have some impact on performance. The hierarchy and size of your classlibraries and forms. A splash screen in a large classlib will take more time to display than one that has no depenencies on other classlibs and is defined in a single form, since VFP simply only reads the form part rather than a whole classlib and other class dependencies.
>
>In short, yOu can really optimize your application performance by using a aplication loader...
>
>Walter,

I always place executables locally.