Solved Failing to save change made from MS Access Front End to SQL Server Cloud (1 Viewer)

[nector]

We have a pricing table which is linked from access by ODBC link tables to SQL server cloud , now this table is required to change the prices regularly , but whenever we want to do the changes we always receive a message that the table is being edited by another user even if there is non , and suggest to drop the changes and also the same goes with the product table

Any solution here

 

[Josef P.]

My guess is that a table with float data fields and no timestamp data field is being used.

 

[GPGeorge]

We have a pricing table which is linked from access by ODBC link tables to SQL server cloud , now this table is required to change the prices regularly , but whenever we want to do the changes we always receive a message that the table is being edited by another user even if there is non , and suggest to drop the changes and also the same goes with the product table

Any solution here


View attachment 113123

In order to work most effectively with SQL Server linked tables, it is highly recommended that you include the "TimeStamp" or "RowVersion" field in each table. You can find many online references that explain what a TimeStamp field is an why it is especially useful in Access Linked tables.

You should open SSMS and add the field to the linked tables where it is needed.

Some developers just default to adding it to all tables; others are more inclined to add it to tables which are updated regularly in Access and which may be in use by more than one user at any given time. In either scenario, it helps keep track of changes so that updating can be done via forms.

 

[Minty]

You can also get that type of error if you opened that form from another form (possibly a continuous lookup form?) with the same record on it in an editable state.

You are now trying to save changes to a record whilst having it open for possibly no good reason on another form.

 

[nector]

GPGeorge & Minty

Thanks you so much to you valuable professionals , the timestamp field has sorted out the problem, this has been a thorn or nightmare for us for sometime.

Regards

Chris