>Hi All
>
>I have always distributed my apps by placing the exe, dlls, etc on a server. The workstation setup was a merely mapping a drive and placing a desktop icon pointing to the files on the server. Every workstation ran the app from the server files.
>
>Lately I have begun to rethink my thin client approach. My apps have gotten larger, data files are larger, number of concurrent users has grown. After migrating an exe to VFP7 and Win2k, we are starting to experience random and non reproducable errors. One example is a record lock failing to release, sometimes there are data issues.
>
>So, would I be better off to set up some sort of workstation configuration? How would I do this? Maybe c:\myapp with it's own config.fpw file and other files. Should I put a copy of the exe here? and the dlls?
>
>Of course the disadvantage is maintenance. Now I only have to drop an updated exe on the server.
>
>Your thoughts and opinion would be appreciated.
>
>Thanks
>
>Donald Lowrey

Donald;

My opinion is if you only have a few users ( 1-5) and there is not a lot of demand on the application (usage) an exe on the server is alright. However, if you have even moderate use of your application it is better to load the exe, etc. on the client’s machine. This will enhance network performance among other things.

You can create loader programs to load the latest version of your exe on the client machine thus reducing the complexity of maintaining revisions.

Tom