Results 1 to 7 of 7
  1. #1
    Star Lounger
    Join Date
    Jun 2003
    Posts
    60
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Write Conflict (Access XP)

    I wonder if anyone can help me. I am currently working on an access front end with a SQL database.

    On some machines and currently this is 2, whenever anyone saves and moves to a new record the write conflict error is shown, however the same changes can be made on a different machine 1 of another 3, it saves without problem.

    If you have any ideas at all please let me know as I am at a complete loss as to why it is so sporadic.

    Many thanks

    <img src=/S/dizzy.gif border=0 alt=dizzy width=15 height=15>

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Write Conflict (Access XP)

    What kind of security is being used? If roles have been set up, it's possible that the users on the machines that are failing don't belong to a group with the necessary permissions.
    Charlotte

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Write Conflict (Access XP)

    Also, what error message are you getting - is it an ODBC error, or are you using ADPs? Also are you getting this error consistently on the 2 workstations, or does it sometimes work and sometimes not. Finally are you using any triggers on the SQL Server tables?
    Wendell

  4. #4
    Star Lounger
    Join Date
    Jun 2003
    Posts
    60
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Write Conflict (Access XP)

    Hi, thanks for the response.

    On 2 machines it's consistent, one 1 machine it's sporadic and on another couple of machines it doesn't happen. There is a trigger on the table which doesn't appear to make any difference whether I remove it or not.


    I am using an ODBC connection but the error message doesn't mention that, it is the usual write conflict message with the option to drop changes or exit.

    Thanks

  5. #5
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Write Conflict (Access XP)

    Hi Beany,
    We've run into this situation a couple of times, and it seemed to be related to triggers being used to archive records before a change, and user and date stamps being applied. It also seemed to have to do with Access subforms and the saving of a main form record immediately followed by an insert of a new subform reocrd.
    Is it happening when edits are made to an existing record, or when new records are being added?
    Also, are all PCs on the same version of Windows and MDAC?
    Finally, as Charlotte asked, what sort of security do you have with SQL Server, and are all users in the same security group?
    Wendell

  6. #6
    Star Lounger
    Join Date
    Jun 2003
    Posts
    60
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Write Conflict (Access XP)

    Will try to answer all the questions in some semblance of order:

    All the users are in the same security group.

    All PCs are on the same version of Windows, however we tried re-formatting one of the pcs that had the problem originally and with a re-format the problem went away. Am probably more confused than ever now!!!

    I have tried removing a trigger and testing it and adding it back and it makes no difference at all on the PCs that have the problem. Am inclined to think that it is the build of the machines that's causing it. Do you have any experience of this?

    Thanks

  7. #7
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Write Conflict (Access XP)

    I do have some experience, and it wasn't much fun. I start to suspect MDAC issues if you can rebuild the machine and have the problem go away. You might try the MDAC Version checker described in <!mskb=301202>Microsoft Knowledge Base Article 301202<!/mskb> and see if you have different versions on the workstations that works from the workstations that get the error.
    Wendell

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •