It was an error message from Microsoft SQL Server Managment Studio
front end....not technically a sql message but i would hope that it
would handle error messages decently.

As for the select statement that has been pointed out by two people
now I don't see it being a problem in the application, but I am
interested in possible solutions and work arounds so that the problem
doesn't exist and so Ii can better at this.
thank you for your time



On Feb 26, 5:48 pm, Hugo Kornelis
<h...@perFact.REMOVETHIS.info.INVALID> wrote:
> On Tue, 26 Feb 2008 06:34:02 -0800 (PST), pyrahna wrote:
> >I get the following error when i try to update a table with the a
> >trigger (trigger script below),
> >"Error Message: The row value(s) updated or deleted either do not make
> >the row unique or they alter multiple rows(3 rows)"
>
> Hi pyrahna,
>
> That does not sound like a SQL Server error message. But rather like a
> message generated by your front end. Many front end programs can get
> confused when triggers modify data. This message sounds like such an
> issue.
>
> However, I saw a different problem with your trigger:
>
> (snip)
>
> > Select @ecr_id = ecr_id, @r_d_release = rd_approval,
> > @production_release = prod_approval
> > from inserted
>
> If an UPDATE statement affects multiple rows, this will cause one (more
> or less at random) of them to be processed. The others will be ignored
> by your trigger. I don't think that is what you want!
>
> --
> Hugo Kornelis, SQL Server MVP
> My SQL Server blog:http://sqlblog.com/blogs/hugo_kornelis