>Hi All,
>
>I am thinking to implement the VFP application and database / tables on the server with a share drive. Example Z drive.
>
>So the client computer that run the application have the Z drive access and directly run from Z drive.
>
>so it minimize the maintenance on each client computer. However in term of speed performance, will it be slow ?
>
>When the app is run from client computer by accessing Z drive, which resource is occupied, server or client?
>
>and what about the tables / DBF, is being copied to local client memory for process? how the tables is being handled ?
>
>Thank you.

If it's keeping the maintenance of the workstations to a minimum is your goal - then you can create a "launcher" program that you put on each workstation that checks the server for the latest version of your .exe - and copies it to the workstation of necessary - then runs your .exe. If you do that then the workstations will autoupdate each time they start the application. As for the data being on the server - once then you will want to be sure to do is make sure any anti-virus software is not scanning network drives - otherwise you could have a serious performance issue.
One thing I've done in these situations is have the application/workstations access the VFP data on the servers via remote views. This way on the workstation you have a copy of the ..dbc and all the remote views - which point to the server and all the VFP tables. If you do this right you can later move to a different backend easily by simply changing the connection string in the remote views to point to something else (like MS SQL Server or PostgreSQL)