Alex,

In the past, we have used something along those lines. We stored all database schema changes in T-SQL scripts in a VFP table, along with a version number for each script. In the SQL database, there would be a "system" table that stored the version number in it. The VFP utility app would compare the version numbers and only run the scripts that were subsequent to the SQL database's version, thus bringing the SQL database up to the latest version. For keeping the SP's up-to-date, they were simply dropped and re-created each time you ran the VFP utility app (the T-SQL scripts for each SP were stored in separate .sql files with a VFP table to keep track of file names).

~~Bonnie


>Bonnie and all,
>
>I think this justifiably falls under Debate on use of SQL Stored Procs.
>
>What method do you use to synchronize procedures in customer databases as your product goes through versions. Is there a way to take a "model" or "master" database to customer and then run a program that automatically compares it to user's database and makes all updates required?
>
>TIA,
>
>Alex