>Hi,
>
>How practical/difficult it is to create a stored procedure that receives a value and then updates several tables with this value. The "trick" is to have some kind of Transaction that if any one of the table's update fails, the entire Transaction is rolled back? If anybody has a segment of code that would go in such a stored procedure, I would grateful for sharing.
>TIA.

Take a look at this blog post showing how to implement transactions and error handling

How to insert information into multiple related tables and return ID using SQLDataSource