Post reply

Write Conflict

  • November 9, 2004 at 1:22 pm

    #65401

    I have an Access 2002 project that is running a SQL 2000 back-end.  I have a Main form based on a table with a sub-form based on a second table.  Records displayed in the sub-form are based on the primary key of the main form.  Whenever the modifications are made to the record in the sub-form I get the following error message:

    Write Conflict

    This record has been changed by another user since you started editing it. If you save the record, you will overwrite the changes the other user made.

    Copying the changes to the clipboard will let you look at the values the other user entered, and then paste your changes back in if you decide to make the changes.

    I then have 3 options:  Save Record, Copy to Clipboard, Drop Changes.

    If I select Save Record the error message stays.  If I select Copy to Clipboard or Drop Changes, the changes are saved and the error message goes away. I've researched this site, the Microsoft site, and countless other sites.  Based on the the information I've found, I've added a timestamp to both tables (the one for the main form and the one for the subform).  Even though I did not have null values for any of my bit fields, I set a default value of 0 for all bit fields in both tables. I installed Office XP Service Pack 3.  I added the following code to OnDeactivate for both forms:

    DoCmd.RunCommand acCmdSaveRecord

    And I added the following code to OnActivate for both forms:

    Dim rs As ADODB.Recordset

    Set rs = Me.Recordset.Clone

    rs.Bookmark = Me.Bookmark

    DoCmd.RunCommand acCmdRefresh

    Me.Bookmark = rs.Bookmark

    rs.Close

    Set rs = Nothing

    None of these things worked.  I can make changes to the records on the main form no problem.  I've been working on this issue for over a week and I would love any assistance on getting rid of this annoying error message.

    Thanks!

  • May 23, 2005 at 2:46 pm

    #560607

    I don't know if you are still looking for an answer, but I had a similar problem with a form based on a view with multiple tables.  The only way I could avoid the write conflict was by creating a Parent form with just the two fields that linked in the original view, then adding a subform with the rest of the details.

     

    Hope that helps!

     

     

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply