>>A loader? As to my knowledge a loader can be a very small exe and the actual code will/can be in a huge app-file. Suppose the small loader is on the local machine and the huge app-file is on the network, would that give more speed? I seriously doubt that.
>>
>>The advantage of not having the exe on a local machine is that an update is simpler. Yes I know that a batchfile could take care of updating, but it's not in my hands here.
>
>No, I meant a small exe which would copy the big exe (or .app, doesn't matter) from the server if newer than local (or local is missing), then would run the local. Each user pulls each version of the exe exactly once from the server. May take a hit when new version is up, but that's actually staggered (unless they all log in at the same time).

Okay, now I understand. The principle is known to me, but it's not an option here, unless of course it can be proven that it boosts performance. :)

Still the question is: Is a readonly drive/folder enough or should the file too be readonly? If you don't have a clue, I'll maybe try some tests next week.

Now it's bedtime. Tomorrow a meeting with a new potential customer. ;)