I have played around with the Database Toolkit and noticed the auto-generated stored procedures for Update and Insert actions. The Insert procedures return @@IDENTITY for the PK but we use SCOPE_IDENTITY() for total accuracy. We have found that returning @@IDENTITY can cause confusion ie., return the wrong value, particularly where inserts are made in triggers that are triggered by the initial insert. Any thoughts?

Is row versioning handled in any way for updates?

How is concurrency handled - after checking the generated stored procedures, there appears to be no specific provision made for row version conflicts or generally concurrency checking.

In Strataframe, is the mapping of business object properties to stored procedure parameters handled automatically?

Thanks,

-=Gary