Write conflict

[Guest]

I added two new fields to a SQL table and updated the SQL view that the front
end form is linked to, I added the new fields to the forms and when I attempt
to update, I receive a write-conflict error, however, I am using a Test
database that no one else is working on...what could be the problem? I
appreciate your help.

 

[Brian]

I added two new fields to a SQL table and updated the SQL view that the front
end form is linked to, I added the new fields to the forms and when I attempt
to update, I receive a write-conflict error, however, I am using a Test
database that no one else is working on...what could be the problem? I
appreciate your help.

Presumably by SQL you mean SQL Server. Try adding a column to the table of
type TIMESTAMP.

 

[Guest]

Hi Brian,

I have columns in a table in SQL server that contains a getdate() and a
unique identifier but I still need to add a timestamp field?

thanks, P

 

[Brian]

Hi Brian,

I have columns in a table in SQL server that contains a getdate() and a
unique identifier but I still need to add a timestamp field?

thanks, P

Correct. If a table contains columns with approximate data types, it can be
unclear to Access as to whether or not an update has occurred, hence this
error. If the table contans a timestamp column, Access will use it to
determine for sure whether there has been an update, and the error will go
away. It's purely an internal thing, you don't need to explictly use the
timestamp column for anything.