>While I haven't tried it, my guess is that if you executed the line of code as a pass-through command to your sql 2005 provider...
>
>

>string cMyCommand = "INSERT INTO Mytable OUTPUT Inserted.MyIdentityCol VALUES ('whatever')";
>

>
>I 'believe' it will give you back a one-row, one-column result set with the key value. If that does work, it's better than having to make another round trip back to the server to get the new ID value using scopeidentity.

I will keep you inform on this. I am having all kinds of problem with the packaging issues presently trying to upscale some data to SQL Server. Once I resolve all of that, I will be able to test this.