>>>>>1. To run the shortcut from the server from the end user computer
>>>>>2. Or need to copy the exe, and the library files to the user computer.
>>>>>
>>>>>Which is faster and recommended method?
>>>>>
>>>
>>>>Time is passing, tech is advancing. I might suggest otherwise in the past, but today I think running from the server is a fairly good option.
>>>
>>>Even if tech advances have made running from the server bearable more often, given the small effort needed for going with established best practices like loader and local RO/pure lookup table caching for best speed possible for DBIsam access tools like vfp, I think "fairly good" should not be advised ;-)
>>
>>Wish I could understand what you are saying :)
>>
>>What is that "established best practices" and why are they "best"?
>
>For DBIsam:
>R/O files put on local client (for instance with a loader) I consider best practice. W files on client and some kind of replication process I consider not best practice unless forced by connection temporarily being unavailable (road warrior scenario), unless used only for temp caching like vfp data buffering in cursors. For vfp exe/app files, which are DB files as well, at least Tore and Wiki seem to agree ;-)
>
>Reason:
>Except for (some) scenarios where server and client run on the same physical HW (some kind of VM setup) it should be given that client "local" file access is faster than client accessing server files.
>
>Accessing files faster gives a more profound speed boost in DBIsam technology compared to C/S, where the amount of info transferred between server and client is minimized.

I don't understand what you are trying to say. I only understood it was your best and that is OK.