Write Conflict When Trying To Update Table

[jo15765]

What's really curious is the error message. I'd expect a permissions or a read-only error depending on circumstances. I've never seen the write conflict error with a table opened directly and nothing else open. When you run the update query, it's an Access query against the linked table, or a pass through query running on the server?

The update query is an access query against the linked table.

[jo15765]

It seems this issue occurred when I added a bit column to my SQL Server 2008 R2 table. (I have a copy of the table before I added that column, and when linked it no errors are thrown. BUT anytime I link in the table with the bit column it throws errors. The values for the bit column are either 0 or -1 and ALL columns have one of these two values.

I added the bit column to hold the value of a checkbox - is there a different field type I should use for this? Access Interprets the field as a Yes/No type.

[Bulzie]

Maybe try Int? Search on "SQL numeric data types".

Before you change datatype, make sure you have a good backup. Maybe just add a new field to that table and use an update query to copy over the values. Then try to change it in the new field to make sure it keeps the -1 and 0.

[jo15765]

Maybe try Int? Search on "SQL numeric data types".

Before you change datatype, make sure you have a good backup. Maybe just add a new field to that table and use an update query to copy over the values. Then try to change it in the new field to make sure it keeps the -1 and 0.

That resolved it!

What is Access hangup with bit fields?

[pbaldy]

Interesting. I link to tables with bit fields frequently. I always make sure the field has a default value though.

[RuralGuy]

I marked this thread as *Solved* for you using the *Thread Tools* at the top of the thread.
https://www.accessforums.net/showthread.php?t=1828