I'm experiencing a problem trying to insert into a table with a computed column with an index on it.
I'm not trying to set the value of the column in question, I'm just trying to insert into the same table.
I searched the forum and found some other cases of this, but it doesn't look like they were resolved as the issue was unable to be reproduced in most cases, or the original poster never responded.
I am able to reproduce this consistently on a SQL Server 2000 database.
If I do nothing, the SET ARITHABORT ON is not present in the statement it tries to run.
If I call "DataAccessAdapter.SetArithAbortFlag(true)" before the save, it DOES change the SQL to include SET ARITHABORT ON but I still get the error anyway, and I am at a loss to explain this.
If I subclass my own DataAccessAdapter and force it to execute "SET ARITHABORT ON" on the same connection as a seperate call before I call the save, the insert does succeed, but I don't think this is an ideal solution.
I have attached a zip file containing my generated DAL, 1 unit test, and a backup of the database in question so you can see this in action.
Details: Latest version of 2.5 final, downloaded today.
SQL Server 2000
Adapter Scenario
Nothing customized or complicated in any way.
I've left out the stack trace and emitted SQ in this case because they seem very redundant with the information above, but I'll be happy to provide them if they'll be of value.