An Access Write Conflict message does not always mean that another person is using the database. You may have the same record open in a table and a form, with both objects holding edits. Treat the message as a record-level conflict to investigate rather than a reason to force your current view over the saved data.

Note the record's identifier and the Access objects currently open. Identify which fields you intended to change in each. Do not rely on a visible name if several records can share it.

Check whether two of your windows address the same record

Microsoft explicitly documents that two objects, such as a table and form, can attempt to write the same record in one Access session. In that case, the apparent other person is you. The dialog also occurs with competing users, so the single-user explanation should be checked against the open objects rather than assumed.

For example, one form may contain a revised contact label while a table view contains a changed internal note for the same ID. Determine which changes have actually been saved and which remain in the competing view. A window still showing your typing is not proof that those values are the database's current record.

Preserve your proposed values before deciding

The dialog's Copy to Clipboard option copies your entire edited record, then shows the other saved changes. Save that copy in an appropriate private working note before copying anything else. Save Record can overwrite the other changes; Drop Changes keeps the other saved version instead.

Compare the proposed values with the saved record field by field. Keep the record ID with the comparison, and account for both intended changes rather than choosing a whole version solely because it is visible in the active window.

Once the conflict is resolved, return to a single intended editing route for that record and apply only the remaining agreed correction. Reopen the record to verify its saved values. If the problem recurs without another visible edit, record the exact form and action for the database maintainer; this basic check does not diagnose every programmatic or backend cause of a write conflict.

Sources: Microsoft: Access Write Conflict dialog.