Sure. You need to make sure you save the @@identity value before you do anything else. FWIW, I don't see why one would use triggers for this sort of thing anyway...

< JVP >


>But if the table where the record is being inserted by the stored procedure has an insert trigger that inserts records into other tables, and those tables have identity fields, won't @@identity return the identity value of the last table that had inserted records?
>
>>>>
>>I understand there are potential problems using Identity fields in SQL to generate a PK.
>>
>>1. Trying to return value with @@identity may give value for insert on another table
>><<
>>
>>Not if you use a stored procedure to add records. After the insert, assign the value of @@Identity to an output variable. Or, just return @@Identity.
>>
>>
>>< JVP >