>We are having a little debate where I work regarding FOX. All of our apps now 2.5DOS/2.6 Win/5.0 reside on servers. The programs are run over the network to access the data.
>
>Our boss wants to run all the exe's local and access the data remotly. I think that this will create more network traffic since all of our querys now have to have the data sent over the network to be processed by the local exe.
>
>Does anyone have any experience with this? All of our tables are Fox so C/S would involve ODBC.
>
>Thanks.
Similar to what others have already said but AFAIK, if you are using Fox tables to store data and not something like SQL Server, your current setup should generate MORE network traffic, not less. When you store both data and .exe in the file server, each time a client machine starts the app, the whole app is transferred over the network to the client machine's memory for loading and than the appropriate data files also. If you offload the .exe to each client, it wouldn't need to use any network traffic, only when data is called from the program since data is still on the server.
One huge benefit you get from storing the program in the server for shared access is program updates. Each new version doesn't have to be recopied to each client (like what others have already said). My experience doing both ways have been that if your client machines are slow (especially HD access), you actually get better performance from server-based setup. Otherwise, client-based setup is better.

HTH
John.