write conflict

[Walter Levine]

I am using a stored procedure to update an sql server table from an Access
front end.
When I move off the record, I get a "write conflict" message offering to
write the new data, copy to the clipboard or discard,
Is there any way to surpress the message.
In google, there is stuff about putting a timestamp field in the table, but
that doesn't work.
Thanks for any help
Walter

 

[Sylvain Lafontaine]

Often, this is caused by a missing primary key.

You can also make a check at the Unique Table and Resync Command properties.
Personally, I use often a dummy SP witht the wrong number of parameters as
the Resync Command. Access see that it cannot use it and revert to the
default ADO resync behavior, which is simply to reuse the same data without
a refresh from the SQL-Server.

Take a look at the SQL-Server Profiler; you will learn a lot about this
problem and others.

The TimeStamp won't work if you forget to Refresh the list of Tables and
Queries from the View menu of Access.