>>>>There was a neat old trick for this on slow networks: make the exe read-only. It's not network access per se that's slow, it's the checking for locks. Since nobody is changing the exe (but the installer), setting it read-only will just tell the network not to bother with locks.
>>>
>>>Is it enough to have the exe on a readonly drive (or in a readonly folder) or must the file itself explicitly be readonly?
>>
>>Didn't try any but the last, so I wouldn't really know.
>
>No theoretical hunch here?

No, not really, because my only experience with read-only was with physically read-only drives (optical disks, protected floppies) which are by definition slower.

>A customer is complaining about a slow network. There are 250 users synchronically using a vfp app. It probably isn't the vfp app that's causing the trouble, but if it is then I might be of help with this tip. However, the app is in a readonly folder (actually on a readonly drive) and testing would involve the cooperation of network operators and it must not disturb operations.

Any reason why the app doesn't use a loader? Temp files local? Other usual suspects?