>>Duh! Excuse me for the brain lock.<

hehehe ... happens to the best of us. < g >

>>Depends on whether or not the COLUMNS_UPDATED() thing pans out.<

Yeah, I haven't used that, so I can't give you any feedback on it. Keep us posted as to how it goes ...

~~Bonnie




>>I only meant to write a VFP app to use as a tool that you would use to generate the T-SQL script. We do that all the time.
>>
>>~~Bonnie
>
>Duh! Excuse me for the brain lock. That might have been the way to go, and might still be. Depends on whether or not the COLUMNS_UPDATED() thing pans out. If it does, the only thing different between the scripts would be a bit mask variable.
>
>Thanks Bonnie.
>
>>>>Hiya Geo,
>>>>
>>>>One thing you could try is to write a quickie VFP tool to generate the triggers for you. Shouldn't take you more than an hour to do it. This way, you could just compare every field in your trigger, but you wouldn't have to code it all, the tool would do it for you.
>>>>
>>>>~Bonnie
>>>
>>>I've been thinking, "This would be cake in VFP". Unfortunately, VFP isn't in the loop in this one, and it's got to be written in T-SQL. BOb Archer did point out (on the SQL Server forum) that there's a function there, COLUMNS_UPDATED(), that looks like it could be the solution. Don't know yet, because I haven't tested.
>>>
>>>Thanks for the feedback, though.