Re: Global Variables?
From: Russell Fields (RussellFields_at_NoMailPlease.Com)
Date: 03/09/04
- Next message: oj: "Re: simple question re DELETEing in linked DB"
- Previous message: oj: "Re: Help with query (sorting and grouping fields)"
- In reply to: kb: "Global Variables?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Mar 2004 13:45:25 -0500
kb,
Why have a second trigger do this? Can you call a stored procedure from the
first trigger and pass the needed info into it? That would get you out of
the game of coordinating triggers.
FYI, the "inserted" table does not really exist, it is a view across entries
in the transaction log. Therefore, non-updateable. You could, of course,
reupdate the row in the base table, but think about that and recursive
issues before you do it.
Russell Fields
"kb" <anonymous@discussions.microsoft.com> wrote in message
news:214D4B58-B94E-4C79-8948-54C37E2005D6@microsoft.com...
> Is there any way to declare a variable so that I can set the value in one
trigger (that sets a status to indicate a duplicate record) and have it read
into a second trigger (that writes that status to an audit trail?) I've
tried a couple of different ideas to get this status to write correctly and
it doesn't seem to work. The easiest way would be to update the "inserted"
table, but it says it doesn't allow that.
> Thanks
- Next message: oj: "Re: simple question re DELETEing in linked DB"
- Previous message: oj: "Re: Help with query (sorting and grouping fields)"
- In reply to: kb: "Global Variables?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
