Sorry, still not following what you have to send to other developers...

If they're using the picklist, they get the new data anyway, don't they?
For updating these, I typically have the calling application check periodically, rather than have the database push anything out.

If it's a structure change, is it that they need to be notified of the change?
I don't have anything that automatically does this except a habit :)

There are a few commercial products I've seen that are basically wrappers around a change control process - i.e., Generate the script, put it into VSS, check it out prior to making changes, make changes, save file, check it in. The big downside to these, IMHO, is that to take advantage of it as a change control mechanism, you pretty much have to use their interface for all programming.

>Sometimes I will need the data because the table is a new picklist, but sometimes there is just a structure change.
>
>For things like this do you write your own scripts, use public domain products, or commercial products?
>
>Thanks,
>
>>>What is considered the best way to send a new table with its data to other developers that are changing the database at the same time as me?
>>>
>>>Is there a stored proc that inputs a table name and then outputs a script that drops existing if it exists and then recreates possible new structure and then adds data?
>>>
>>>Please link me.
>>>
>>>Thanks,
>>
>>Not sure what you mean by "send...to other developers"....
>>but, since v7.0 you can use ALTER TABLE to change structures, bypassing the need to store data/drop/create/restore data.