>>As far as performance is concerned, what are the tradeoffs and what is the general consensus about installing a multiuser app?
>>
>>I'm assuming that the only difference in performance will be at the time of starting the .EXE. It'll be obviously faster to start locally than off the server, but the downside is multiple copies that need to be maintained, updated, etc
>>
>>But is there more to it? If i've got a 2MB .EXE on a server, will it be CONTINUALLY slower during execution, or has it all been read into memory once it starts and so there won't be any more performance difference from the .EXE started locally?
>>
>>In these scenarios the VFP runtime files will ALWAYS reside locally.
>>
>>Am I right or am I missing something which might direct me to put my .EXE on each local machine?
>>
>>All input welcome!
>
>The truth is that using local Exe you will never get worse speed than in case of server Exe. Theoretically, the delay will really happen on start point only, but I remember some threads here that proved something opposite. Also, there are some tools (here UT Files) which allow to make maintainance eisier (launcher programs). Also, using local executable you may provide robust scheme for multi-user environment, i.e. each users starts from his/her own separate local folder with own resource file, configuration table etc.


Sounds like local is the way to go. I'm having one wierd problem though.

If I put my .EXE locally and make a shortcut to it where the 'Start in' points to the proper network folder, it's fine. However, if I go through explorer and double-click my .EXE on my local drive, in the same directory as my CONFIG.FPW which also points to the network folder (DEFAULT=F:\MYAPP) then it DOESN't work.

It's like the DEFAULT= is having no effect - Any ideas?

Thanx,
Joe