The key that I am using was a primary key when it throws the error. In SQL Server it is an identity field. Since it is a primary key, it is made unique by default. When I take off the primary key from the SQL Server field, it saves fine. Now I do the exact same thing with my other tables without problems thus far.

What I understand you are saying is to remove the primary key designation from this field, and allow the business object to generate the primary key? I would assume you mean to use the RetrieveAutoIncrementPK = true, which is what I am currently doing? So when the procedure inserts it will insert the value into this field without issue or conflict with SQL Server?

Am I understanding this correctly?

Thanks...That makes since.