Do it in a stored procedure, not a trigger. Even better, consider changing the design so that there isn't a dependency between columns in two base tables. Maybe you could derive the same information in a view or query instead.
Scott Pletcher
A trigger is safer than a stored proc. There is no guarantee that a stored proc will be used for all UPDATEs (and/or INSERTs).
Emes
CREATE TRIGGER TRIG2 ON AAA
For update
as
update BBB
set statecode = 1
FROM inserted i
INNER JOIN bbb ON
BBB.phonecallid = i.activityid
and i.deletionstatecode = 2