What?  No-one's picked up on the spelling of "colour" in the original post?

I despair.

I've worked with one consultant from India, and he was very good.

I cancelled an order with Dell last year because, whilst trying to communicate with them during the ordering process,...

By bringing up the subject of religion himself, the author has demonstrated the effect it can have, and the controversy it can spark, by just saying not to mention it.

Irony at its...

If I've understood you correctly, would this be the answer?

INSERT INTO ExportStock (Item_Code, StockFree, StockBlocked)

SELECT Item_Code,

SUM(Units * Sub_Units * CASE WHEN Status = 1 THEN 1 ELSE 0 END),

SUM(Units *...

I just did something similar the other day with Progress arrays, which are returned to SQL Server as a single semicolon-delimited column, and I needed to split out one such...

Steve... could something along these lines (per the link below) be a possible short term solution? This one (the "Sky Magic Eye" at the top of the page) is...

Is the procedure you're view accessing another data source at all? I believe if you have a procedure with, say, a passthrough query in it then it will verify...

Yes, you'll get that error - and definitely a "no no". You're trying to bring back each individual value for that column, and then sum it... which is going...

At first glance it appears you're grouping by OO.OOForcedAmount and trying to sum it.

This would return one row for each different value of OO.OOForcedAmount, and the sum of rows that...

Check the deleted table. If there are records in there (COUNT(*) > 0) and in inserted then it was an update.

If there are only records in inserted, and none...

Sorry... nothing that I can see to avoid the complication, with the calculations being derived (you can't refer back to other calculations in a SELECT statement).

The only solution I can...

Because the straight insert from the inserted table would be a set operation (i.e. would run once with multiple rows in one operation).

When you set the variables, they just store...

It looks to me like you just need to get rid of the variables and put the calculations directly behind the last insert. It looks like it'll probably be...

Can you post the actual trigger as that will help the solution?

If many rows are updated/inserted, the trigger will be called once with all the affected rows in the inserted...

Check out the inserted and deleted tables in BOL... I think that should give you the answer you're looking for. (Look up "inserted tables" in the index.)