>Hi all
>
>I'm wondering what if anything anyone is doing to allow multiple developers to change SQL Server table structures and coordinating these changes via VSS.
>
>To me, the structures of the tables must remain in sync with the application.
>
>I was thinking of creating VFP programs to issue ALTER TABLE commands and checking these programs into VSS. However, I'd want to ensure that only these programs be used to change structures.
>
>Any other suggestions?
>
>Thanks!

It has always been my practice to never alter a table manually, but maintain a dbUpdate.PRG. I group the structure and data changes by application version / build number in IF ENDIF blocks. The at the customer site, when the application frist ran, the dbUpdate.PRG (in the application) is ran. It compares the last version of the application (general stored in a configuration table in the database) to the version numbers in the dbUpdate.PRG. All code that was writen after the last application version get executed. Once the update is complete successfully, the version number if the configuration table gets updated.

This method work with SQL Server and FoxPro table, and others too.

Hope it helps.