>I like Option 1, but i want to ask you some questions:
>When the user clicks on the local icon, Is the EXE file loaded once from server to local pc? or we will have some more traffic on the network ?

The EXE is loaded once. After that the majority of the traffice will be data access. I say "majority" because some people have said there can be some acess of parts of the EXE after the inital load.

>How do you install VFP runtime on a client where you have never installed an EXE?

Create a fake SETUP routine using the setup wizard. This routine will only install a TXT file onto the harddrive of the machines, but will have the side effect of installing the VFP runtime (ensure to check this option). Put the SETUP.exe and all the files onto the server. You then can visit any station that is new and easily install the the VFP runtime.

>My network is small:
>1 Server - 233 Mhz - 32MB (NT 4.0)
>4 Clients - 133 Mhz - 16 MB (W 95)
>What happpens if the number of clients is higher?

No problems. Same setup. I have 180+ users on 45 machines streched over a campus. This technique works well for me. I can even phone new users and talk them throught the VFP runtime setup routine over the phone.


>Thank you very much,

You are welcome.

>>I know of three options:
>>1) EXE on server
>>- everyone gets updates at same time
>>- must wait until all users are off to update exe
>>- easy to admin
>>- no installation except VFP runtime on pc
>>2) loader EXE on each workstation. This EXE checks for a newer program EXE on the server. If it is newer it downloads it to the local harddrive.
>>- next time someone runs your they have the latest app
>>- can update the EXE on the server at any time
>>- more complexe to admin, loader EXE might have problems
>>3) EXE on local pc
>>- no really an efficient option
>>- update to EXE requires programmer to visit each station
>>
>>I prefer option 1 since I can't always trust that I have permission to copy anything onto the local pc.
>>