write conflict error, data changed by another user (with Sybase)

[Rolrox]

I've discovered that in Sybase, I had a field/column whose datatype was defined as "bit" which also permitted NULL values.

When I changed this to smallint, the write conflict went away.

[missinglinq]

Is there a question here?

How does this relate to MS Access, the focus of this forum?

Linq ;0)>

[NeoPa]

Equally confused by this thread, but it certainly doesn't qualify as an Insight, so I moved it to Answers.

Rolrox, if you can add something so this makes sense as a question please do. Otherwise it's just a strange statement.

[Rolrox]

It is an "insight".. . The numerous posts on the "write conflict" didn't solve my issue. Others wrote about:-

• add a timestamp
• datatype fragility
• multiple data tables being saved

What Iearned is that, specifically for Sybase:-

• "datatype" defined as "bit"
• permitting nulls
• actual data content being "NULL"

One will get the same behaviour.

I venture that:-

• Sybase dissembles as by definition a bit is either on or off, and cannot hold a null;
• The ODBC however tells Access that the definition permits NULL
• Sybase sends, somehow, the augmented value
• Access converts this on receipt (the "fragility" that somebody else mentioned)
• When saving, Access looks however not at the "converted" value, but at the raw value that somehow also conveyed the NULL.

As this caused me grief, I thought others would benefit; though I noticed that the older posts were marked as CLOSED, so I thought I would offer the insight here, expecting that someday, somebody might again search for "write conflict" in Access.

[NeoPa]

You may want to check out the FAQ about what constitutes an Insight on Bytes. The FAQ link should be available on every page.