Using SQL's "bit" type?

[Guest]

I added a bit-typed field to one of my tables, which is accessed via a linked
table in an MDB project. As soon as I update the link in order to "see" the
new field (which maps in as a Yes/No type), any attempt to save any record
after any change results in an error saying that someone else changed the
record.

This is, of course, not true. I assume there's some sort of incompatibility
here? Is there a proper way to use bit fields in linked tables?

Maury

 

[gandalf]

I believe it had to do something with the nullability of
the bit-field.

I think you need set the default value for the column in
sql server to either 0 or 1 or make it non-nullable.

 

[Dirk Goldgar]

I added a bit-typed field to one of my tables, which is accessed via
a linked table in an MDB project. As soon as I update the link in
order to "see" the new field (which maps in as a Yes/No type), any
attempt to save any record after any change results in an error
saying that someone else changed the record.

This is, of course, not true. I assume there's some sort of
incompatibility here? Is there a proper way to use bit fields in
linked tables?

Maury

A Google Groups search quickly turns up references to this KB article:

http://support.microsoft.com/kb/280730/EN-US/

 

[Guest]

I think you need set the default value for the column in
sql server to either 0 or 1 or make it non-nullable.

Ok, let me try that, thanks!

Maury