June 8, 2007 at 4:36 am
Hi,
I am new to triggers and have been confused by reading various articles on how to create an update trigger.Im looking for help with creating an update trigger on a table. I need to put a trigger on a table (called table A) which has a date column. If that date is then updated I need to update another table, table B so that it indicates that the date has changed for a particular file, this done by changing the flag to 1 if there is a change and 0 if no change. Both tables A and B have a common column called code.
Table A
Code | Date |
111111 | 01/01/2007 |
222222 | 02/02/2007 |
Table B
Code | Flag |
111111 | 0 |
222222 | 1 |
Thanks you very much
Rookie
June 10, 2007 at 9:21 pm
Sab,
Would you mind showing us the code you've tried so far, please...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 2:46 am
Hi Jeff,
Many thanks for taking the time to reply, below is the code I tried. After reading a few books/web sites its the best I could come up with and as I am totally new to triggers I feel that I maybe way off.
CREATE TRIGGER Flag_update
on table_A
for update
as
if Update (Table_A.[Date])
Begin
update table_B
Set Flag = 1
From table_A join inserted i on table_A.Code = inserted.code
end
Thanks again
Rookie
June 11, 2007 at 7:24 am
Already posted this on the PM you sent me... thought I'd share the solution I think you are looking for...
CREATE TRIGGER Flag_update
on table_A
for update
as
if Update (Table_A.[Date])
Begin
update table_B
Set Flag = 1
From table_B join inserted i on table_B.Code = inserted.code
end
--Jeff Moden
Change is inevitable... Change for the better is not.
June 11, 2007 at 7:26 am
Thanks Again Jeff
Rookie
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy