Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

How do you suppress a WRITE CONFLICT message.

Discussion in 'Information Technology' started by Roman B., Jul 28, 2006.

  1. Roman B.

    Roman B.
    Expand Collapse
    Guest

    Anyone know how to suppress a WRITE CONFLICT message box from showing in an
    access DB? We know what is causing it to show up but want to keep the message
    from popping up, because it really isn't causing a problem.


    Any help is much appreciated.
    thanks

    R
     
  2. Loading...


  3. IF it's a table write conflict message just in the immediate window do

    DoCmd.SetWarnings False

    Then when your done

    DoCmd.SetWarnings True

    If this is not what you mean i Apologize for misunderstanding.

    --
    ===============================
    Gary Townsend
    Database & Application Developer
    Spatial Mapping Ltd.

    "Roman B." <RomanB@discussions.microsoft.com> wrote in message
    news:B2509092-2393-4154-B5AE-67A4CEE36A0C@microsoft.com...
    > Anyone know how to suppress a WRITE CONFLICT message box from showing in

    an
    > access DB? We know what is causing it to show up but want to keep the

    message
    > from popping up, because it really isn't causing a problem.
    >
    >
    > Any help is much appreciated.
    > thanks
    >
    > R
     
  4. Albert D.Kallal

    Albert D.Kallal
    Expand Collapse
    Guest

    "Roman B." <RomanB@discussions.microsoft.com> wrote in message
    news:B2509092-2393-4154-B5AE-67A4CEE36A0C@microsoft.com...
    > Anyone know how to suppress a WRITE CONFLICT message box from showing in
    > an
    > access DB? We know what is causing it to show up but want to keep the
    > message
    > from popping up, because it really isn't causing a problem.


    The above is contradiction in logic. If you know what is causing the
    problem, then you would fix this. That message means that some other person
    (or code that you run) has modified the record, and if you save changes,
    then some data will be lost...

    I cannot in any good standing recommend that you ignore this message. I
    would strongly suggest that you fix the code....

    If you have a form sitting on one record, and you

    a) launch another form that might edit the data
    or
    b) run some sql or update code that does NOT USE the forms
    controls to modify the data,

    Then, simply FORCE a disk write of the current form to flush out all changes
    to disk, and THEN open that other form (a), or then run that code (b).

    Simply put a

    me.Refresh *right* before you run the offending code that modifies the data
    (or opens another form that might modify the data). That way, then you (or
    your code) returns to the form...there is not pending disk writes...and thus
    no write conflict that can occur...

    I can't imagine you are in a position to simply ignore the message, as that
    message means some of your data is about to get overwrite and not saved.....


    --
    Albert D. Kallal (Access MVP)
    Edmonton, Alberta Canada
    pleaseNOOSpamKallal@msn.com
    http://www.members.shaw.ca/AlbertKallal
     
  5. aaron.kempf@gmail.com

    aaron.kempf@gmail.com
    Expand Collapse
    Guest

    a) dont use MDB for anything it isn't reliable enough for a single
    record and a single user.
    b) dont use MDB for anything it isn't reliable enough for a single
    record and a single user.
    c) dont use MDB for anything it isn't reliable enough for a single
    record and a single user.
     
  6. aaron.kempf@gmail.com

    aaron.kempf@gmail.com
    Expand Collapse
    Guest

    you CAN upgrade your app to Access Data Projects and things are a lot
    more reliable.

    SQL Server sprocs and views are a thousand times more powerful than
    silly old mdb files
     

Share This Page