>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.

This works. Here is the approach I am using:

                oCommand.CommandText = cSQL

                ' In SQL Server, we can get the primary key as is
                If nBackend = 2 Then
                    oCommand.CommandText = oCommand.CommandText + "; SELECT SCOPE_IDENTITY() ;"
                End If

                ' Only add the parameters if we have some
                If oParameters2.Count > 0 Then
                    For Each oDataParameter In oParameters2
                        oCommand.Parameters.Add(oDataParameter)
                    Next
                End If

                oDataAdapter.SelectCommand = oCommand
                oDataAdapter.SelectCommand.Connection.Open()
                oDataAdapter.SelectCommand.ExecuteNonQuery()

                ' In SQL Server, we can get the primary key as is
                If nBackend = 2 Then
                    nPrimaryKey = oCommand.ExecuteScalar()
                End If