in addition to Andrew, I think you can check for the specfic column as well.

see
http://groups.google.com/group/microsoft.public.sqlserver.programming/browse_thread/thread/af92ec70c1febf6b/6cf93cbe4776f30e?hl=en&lnk=st&q=inserted+Employee+trigger+sloan#6cf93cbe4776f30e
for the original post..

here is a sample, you could alter to fit your need.

Notice the "if update(HireDate)"

Notice (as Andrew mentioned) that the trigger runs ONCE per set. So if you
update 10 rows, the trigger runs once (this is the most common error I see)

And finally, Notice that the inserted table gets populated on INSERTS or
UPDATES ( if you define it as such with the "For Update, Insert" clause).



Here is a generic example. This runs for Employees, and the HireDate of
"01/01/2000". (Obviously a silly example, but you can figure out your own
needs based on the sample)
This assumes a dbo.Employee table with a EmployeeUUID (guid, primary key)
and HireDate (datetime) column.


CREATE TRIGGER trgExample1
ON dbo.Employee
FOR UPDATE , INSERT
AS


BEGIN


IF UPDATE(HireDate)
BEGIN


--print '..(inserted).............................................'
-- select * from inserted
--print '----------------------------------------------------------'


Select *
FROM
dbo.Employee emp INNER JOIN inserted ins
ON ins.EmployeeUUID = emp.EmployeeUUID

AND inserted.HireDate = '01/01/2000' --<< this would be your
resolved flag here


--print ''
--print '/Start Trigger Info/'
--print 'Trigger Fired (Should only fired once, even for bulk update)'
--print @updateCount
--print '/End Trigger Info/'
--print ''


END


END


Go




[quoted text, click to view]

problem with that is that i think the interface builder for my
database is updateing the database records with their own information
if other things are updated and well that would work even if a 0 is
written the first one worked fine thx andrew