Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Access / SQL Server 2000 Write Conflict error

Access / SQL Server 2000 Write Conflict error

Scheduled Pinned Locked Moved Database
helpdatabasesql-serversysadminquestion
2 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    StyleGuide
    wrote on last edited by
    #1

    Hi there, I have an Access App with a SQL Server 2000 back end. When I Modify a table, then refresh the table in Access I get a 'Write Conflict' error message, even though I'm the only user logged on. This happens when I refresh the linked table in Access and also when I delete the table in Access, and then refresh. It only happens to existing rows, not new ones, and I've created a new table based on the current one, but still get the same problem. I don't get the problem if I change a row in SQL Server. I've also taken the mdb offline and online again, hoping this would reset the link. It still doesn't work. Any ideas? Thanks in advance Jon

    S 1 Reply Last reply
    0
    • S StyleGuide

      Hi there, I have an Access App with a SQL Server 2000 back end. When I Modify a table, then refresh the table in Access I get a 'Write Conflict' error message, even though I'm the only user logged on. This happens when I refresh the linked table in Access and also when I delete the table in Access, and then refresh. It only happens to existing rows, not new ones, and I've created a new table based on the current one, but still get the same problem. I don't get the problem if I change a row in SQL Server. I've also taken the mdb offline and online again, hoping this would reset the link. It still doesn't work. Any ideas? Thanks in advance Jon

      S Offline
      S Offline
      StyleGuide
      wrote on last edited by
      #2

      Solution - a new column was a bit data type : all existing rows require a value of 0 / 1 in that column.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups