Write Conflict! Can't save a record.

[MichaelK]

Access 2002. I have a table linked from SQL Server.
When try to enter values in any field on the record it giving me a Write
Conflict! message.
This record has been changed by another user since you started editing it,
e.t.c.
Save Record button is disabled, and only 2 options: Copy to Clipboard and
Drop Changes.

I know for sure nobody else using this table. Table has 1 key field, which
is actually the record number.
No rules, no triggers, no formulas in fields.
Just a simple data table like all other tables linked from SQL in this
database,
and only this one behaves like this.

Any ideas why may it happen?

Regards,
Michael

 

[Albert D.Kallal]

Two things:

1) make sure the table in question has primary key, and this is exposed
to ms-access
2) make sure the tale in question has a timestamp field, and this is also
exposed to ms-access.

 

[MichaelK]

Albert.

Primary key is visible, if view this table in design mode.
I guess can consider this exposed.

Absolutely have no idea what you mean by "tale in question has a timestamp
field".
Where is this tale, and how can I check it?

Michael.

 

[Albert D.Kallal]

Absolutely have no idea what you mean by "tale in question has a timestamp

field".
Where is this tale, and how can I check it?

table......(type-o...I missed the b key!!)

Make sure a sql time stamp field is also exposed....

Fix the above....

IF that does not make it work...then check the following...

ACC2000: Write Conflict Error When You Try to Update Records in a Linked SQL
Server Table

http://support.microsoft.com/?id=280730

 

[MichaelK]

Thanks Albert.

Apparently my problem was that I added a bit type field to the existing
table with default value 0.
Updated all records with 0.
Working fine now.

By the way never had a problem with the tables without timestamp fields.

Anyway, thanks again.
Michael

 

[Albert D.Kallal]

By the way never had a problem with the tables without timestamp fields.

It is more noticeable when you have a form + sub-form.

Ms-access uses the timestamp field to figure out if the record has been
updated. If access can't do this, then it then drops back to a field by
field comparison....

I do suggest you make it a habit, I seen many a forms/subforms not work
without having timestamp fields....