I see two problems here...
1. How to automatically update the views when the structure of tables is changed
2. How to update the latest version of the exe & db* to each client

1. I would use the GenDBC program which comes with VFP to maintain my views. This way you can make the modifications in the generated prg file and run it again to give you a new dbc file

2. Couple of ways to fix this. The easiest would be to send an e-mail to all the users with a link to the setup.exe on the server. If the users are less technical (for an installation).... have the shortcut on the user's desktop point to a program on the server which compares the date-time of the exe on the server and the user's local machine and updates the local copy if it is old before running the local copy of exe.

Kamal


are putting a VFP 6.0 app out in 40 offices around the world with SQL Server 7.0 as the backend. The nature of the beast is; we are still doing development on the app. So we need to send updates out the the offices we have already setup. Updating the codse is no problem. The problem comes in when we change the structure of the SQL tables. Is there anyway to automate the updating of the remote view structures?
>
>Changes can be anything from field size changes to adding and deleteing fields.
>
>Ideas?
>
>Thanx