>As far as I understand trigger shouldn't be recursive by definition. Instead of this you can just create some method ModifyOtherRecords and call it each time after record has been modified (e.g. in cmdSave.Click event)

You're right, I just wanted to ensure that the information on the table will allways be consistent, that's why I was using triggers. With the method option, I still have to call the method, and this will depend of the environment, but the trigger option would allways work, no mather if you made the chnage from a browse window, a program or a form, and with triggers you never forget to call the method.

Thanks