Strange Write Conflict message when trying to change data

[Thomasso]

Hello everyone,

I work on a MS Access app based on MS SQL 2019. I have just run into this strange thing...

I have a table tblShipments, which contains columns DateSent and DateReceived. When I process the shipment for the first time, it gets created automatically by a VBA code in the background, including the DateSent.
Then I want to manually input DateReceived when I check that the item has been delivered to my customer.

However, I'm not able to change the field (or any other field for that matter), with this associated error:
https://support.microsoft.com/en-us/...2-b2a3d73ee775
(Save Record option being grayed out).

I don't understand this, because I am the only one using the database, everything is closed and so on.

This happens in both forms and also when I try to manually update the value in MS Access linked table (from SQL Server).

BUT, I am perfectly able to update any values directly within MS SQL Server! So this really seems more like an Access issue to me.
And this definitely worked before. I did many changes to the system today (on SQL side, also VBA side, not the table design though), so it's quite impossible to pinpoint a single one to connect with this issue...

Could you please advise what could be the reason here?

Thank you very much,
Tomas

[Thomasso]

EDIT:

I just realized that this is happening with more tables, but not all of them.

I tried to restart the SQL Server and Compact & Repair the Access app, which did not help.

[Minty]

Have you relinked the tables without it picking up the primary key identifier on the tables?
Without that Access can't update tables as it can't identify the record uniquely to perform the edit.

[Gicu]

Do you have\added any bit fields into the SQL table? If yes, make sure they all have Allow Null=No and set a default value to 0 (or 1 as required):
https://stackoverflow.com/questions/...write-conflict

You will also need to update the existing records (UPDATE BitField SET BitField = 0 WHERE BitField Is Null).

Cheers,

[isladogs]

Same response as Vlad but with a link to my own web article: Write Conflict Errors (isladogs.co.uk)

[Thomasso]

Thank you for the suggestions. I made sure that there are no BIT fields with NULLS enabled,but that did not help (I only had one BIT field with allowed nulls before within the entire database anyways, and that was completely unrelated to this particular Shipping operation).

However what did help was to add a TIMESTAMP column to every table (and also add those columns to views based on those tables).

So thanks a lot! :-)

Tomas