Write conflict when SQL table contains BIT field

[Mike]

recently I linked a SQL table (SQL7) into an Access (2002)
application that contained a BIT field. I was able to add
new records but I could not edit records. I get a 'Write
Conflict, someone else is tryig to update the record...

If I change the BIT field to another data type (VARCHAR)
then I am able to edit records in Access. I know in the
past I have been able to edit records containing a BIT
field. I have a feeling that one of the recent MS Security
patches may be the cause. Has anyone else experienced this
problem?

Thanks,
Mike

 

[Rick Brandt]

recently I linked a SQL table (SQL7) into an Access (2002)
application that contained a BIT field. I was able to add
new records but I could not edit records. I get a 'Write
Conflict, someone else is tryig to update the record...

If I change the BIT field to another data type (VARCHAR)
then I am able to edit records in Access. I know in the
past I have been able to edit records containing a BIT
field. I have a feeling that one of the recent MS Security
patches may be the cause. Has anyone else experienced this
problem?

Try adding a Timestamp field to the table on the server. This is not a bad idea all
of the time, but any time the table has a DataType that Access cannot translate
exactly it becomes a virtual necessity.

 

[david epsom dot com dot au]

Solution is TimeStamp: problem may be that this bit field
allows nulls and has records with null values.

(david)