General discussion

  • Creator
    Topic
  • #2179291

    Issue with Access 2003 & SQL

    Locked

    by tim_kelley ·

    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?

All Comments

  • Author
    Replies
    • #3137821

      Reply To: Issue with Access 2003 & SQL

      by tony hopkinson ·

      In reply to Issue with Access 2003 & SQL

      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.

    • #3137819

      Reply To: Issue with Access 2003 & SQL

      by tony hopkinson ·

      In reply to Issue with Access 2003 & SQL

      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.

    • #3137914

      Reply To: Issue with Access 2003 & SQL

      by tim_kelley ·

      In reply to Issue with Access 2003 & SQL

      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.

    • #3136056

      Reply To: Issue with Access 2003 & SQL

      by tim_kelley ·

      In reply to Issue with Access 2003 & SQL

      This question was closed by the author

Viewing 3 reply threads