Could you be more specific? What is the source of this error?

Three things I would check:
1. Check your views in SQL Server for any syntax errors. T-SQL (which is what SQL Server uses) has slightly different syntax from Access SQL.
2. Does your view have any indexes? If you link a view to your Access front end, it’s typically read only unless you create a view on the server with SCHEMABINDING and include a clustered index.
3. Do you have VBA code that references “TendersOnTableV” and not “DBO_TendersOnTableV”? If so, the easiest thing to do is remove the “DBO_” prefix from your table/view name in Access, that way your references in code will still work.

Hi Halkawt

Seeming's it works fine on another laptop, sounds like the laptop might be the issue, a few months ago I had an issue with the system time being out of sync access didn't like it at all, and yes I do have auto sync on?, but it was out of sync had to manually sync it.

Hope you find the problem.

If your database works on one computer and not another, check that you have a File DSN and not a Machine DSN. File DSNs follow the database regardless of the machine, machine DSNs are tied to the machine that originally created it.

Since the same ACCDB works on another laptop, that points more toward something local on that machine rather than the database or SQL Server itself.

A few things I would try. First, relink the table fresh on that laptop and make sure the correct ODBC driver is installed. Also check whether you're using a File DSN, Machine DSN, or a DSN-less connection, since Machine DSNs are tied to a specific computer.

You might also want to try linking directly to the SQL Server table or view with the user name and password saved in the connection string, just as a test. There has been some discussion lately about credential caching issues in Access. A common trick is to open a connection once, provide credentials, then close it and let Access reuse the cached login for the session. If that cache isn't behaving properly, it can suddenly prevent inserts or updates even though nothing changed on the server.

Also double-check that your ODBC driver version matches the working machine, for example Driver 17 versus 18, and make sure your Windows or SQL login hasn't changed, expired, or lost permissions on that laptop.

If linking directly with saved credentials works, then it likely points to a credential or caching issue specific to that machine.

Thank you so much everyone, Mr. Rechard i did all recommendation you suggested still the issue not fixed!! but I went throgh your youtube videos and start checking my fields i found out i have a filed "ClientAddressDetail" which is value list of ("Iraq, Sulaymaniyah, 46001";"Iraq, Erbil, 44001";"Iraq, Baghdad, 10001") and i did put first choice as default value ("Iraq, Sulaymaniyah, 46001"). this was the issue!!, i removed the default value then it worked record created successfully!! after the record saved then i could select the value list and save it !! in other word it throw this error whenever this field has value before the record creation. i might add my field type in SQL server is Nvarchar (Max). any solution or explanation why that error occuring ?

SQL Server works a little differently from Access when it comes to assigning IDs. Access assigns the ID when the first character is inserted, SQL Server usually doesn’t assign the ID until the record is saved and committed.

ODBC INSERT on linked SQL Server tables in Access Fails
https://www.accessforever.org/post/odbc-insert-on-linked-sql-server-tables-in-access-fails

See: Access SQL Server ODBC Problems

Mr. Alex and Mr. Richard, Thank you so much. i appreciate your support.