>>We're using SELECT @@IDENTITY right after the statement, but we use this only on the tables that don't have triggers. I don't like this solution much, but I don't see a better alternative. IDENT_CURRENT has its own problems.
>>
>>
>>Out of curiosity (and maybe you answered this in another message and I missed it)....why aren't you using SCOPE_IDENTITY?
>>
>>Most of the environments I've been in, IDENT_CURRENT would not have been practical at all, for the reasons you stated.
>
>SCOPE_IDENTITY() does not work calling by itself :( In other words, if we're using Remote Views and tableupdate, I think there is no other choice.
>
>BTW, I think I did ask this question myself some time ago and didn't get an answer...
>
>This is my thread on this topic
>
>Re: SPT, updatable cursor and last identity value Thread #1458392 Message #1458444

Actually, I just re-read Fabio's suggestion
Re: SPT, updatable cursor and last identity value Thread #1458392 Message #1459209

I don't think I've tried that, but it does indeed sounds like a solution and I should have tried this instead of keeping the original code.