>I need to store the reason why a certain field was updated. The reason is specified depending what the user is doing in the application.
>
>My first thought was to create an update trigger but I need to store the reason as to why the field was updated. How can I can get the reason from the application to the trigger without having to create a Reasons Field in the table that is being updated?
>
>Is there a way to pass a parameter to an update trigger?
>
>TIA

Why can't you just have the client populate the reason field before the save?

BOb