Web Development

Ask something
Discussion Locked

Issue with Access 2003 & SQL

0 helpful
6 replies

by tim_kelley

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have created tables in a SQL database and use ODBC to link to the tables in Access 2003. If I change the value of a field in an existing record I get a write conflict dialog stating that another user has made changes to this record. I am the only one using this database so this is not the case. Any ideas what is causing this?

6 replies

by tony hopkinson

The most common cause for that particular error is no primary key on the table. What's it's saying really is it can't find the data that is to be changed anymore. For the chnage it's doing
Update Table set field = new_value, ... where . If the where clause identifies a different record or more likely a set of records in a different order. This message pops up as as an ooher, somethings gone wrong.

by tony hopkinson

ODBC has an option where you can log everything that goes through it (on the dsn set up). Dumpls it all into a named text file.
P.S. if you use it don't forget to turn it off, otherwise your system gets slower and slower and you get less and less disk space.

by tim_kelley

The issue was a bit field that did not have the default value set to something. Access did not like it having a null value.

This discussion is closed to new replies.