Welcome to SPN

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

Sign Up Now!

Update query notifications

Discussion in 'Information Technology' started by John In Palmer, Jul 28, 2006.

  1. John In Palmer

    John In Palmer
    Expand Collapse
    Guest

    Hi all,
    Can anyone tell me how to get rid of the annoying messages that pop up from
    within Access when attempting to run an update or delete query? I would like
    to have the ability to bypass those messages. Thank you in advance.
     
  2. Loading...


  3. strive4peace

    strive4peace
    Expand Collapse
    Guest

    Hi John,

    if you are using code to execute the query, use

    currentdb.execute "QueryName"

    instead of

    DoCmd.OpenQuery "QueryName"

    ~~~~~~~~~~~~~~~~~~~~~~~~~

    if you are using macros or just opening queries from the database
    window, before you run action queries:

    macro action --> SetWarnings --> false
    macro action --> Echo --> false

    then, after you run action queries...

    macro action --> Echo --> true
    macro action --> SetWarnings --> true

    Warm Regards,
    Crystal
    *
    :) have an awesome day :)
    *
    MVP Access
    Remote programming and Training
    strive4peace2006 at yahoo.com
    *



    John In Palmer wrote:
    > Hi all,
    > Can anyone tell me how to get rid of the annoying messages that pop up from
    > within Access when attempting to run an update or delete query? I would like
    > to have the ability to bypass those messages. Thank you in advance.
     
  4. John In Palmer

    John In Palmer
    Expand Collapse
    Guest

    NICE!
    Thank you so very much.


    "strive4peace" wrote:

    > Hi John,
    >
    > if you are using code to execute the query, use
    >
    > currentdb.execute "QueryName"
    >
    > instead of
    >
    > DoCmd.OpenQuery "QueryName"
    >
    > ~~~~~~~~~~~~~~~~~~~~~~~~~
    >
    > if you are using macros or just opening queries from the database
    > window, before you run action queries:
    >
    > macro action --> SetWarnings --> false
    > macro action --> Echo --> false
    >
    > then, after you run action queries...
    >
    > macro action --> Echo --> true
    > macro action --> SetWarnings --> true
    >
    > Warm Regards,
    > Crystal
    > *
    > :) have an awesome day :)
    > *
    > MVP Access
    > Remote programming and Training
    > strive4peace2006 at yahoo.com
    > *
    >
    >
    >
    > John In Palmer wrote:
    > > Hi all,
    > > Can anyone tell me how to get rid of the annoying messages that pop up from
    > > within Access when attempting to run an update or delete query? I would like
    > > to have the ability to bypass those messages. Thank you in advance.

    >
     
  5. Allen Browne

    Allen Browne
    Expand Collapse
    Guest

    Crystal has already answered your question, but if you want more detail see:
    Action queries: suppressing dialogs, while knowing results
    at:
    http://allenbrowne.com/ser-60.html

    --
    Allen Browne - Microsoft MVP. Perth, Western Australia.
    Tips for Access users - http://allenbrowne.com/tips.html
    Reply to group, rather than allenbrowne at mvps dot org.

    "John In Palmer" <JohnInPalmer@discussions.microsoft.com> wrote in message
    news:23F38D4F-ACBD-49E4-AA57-60FFCF95F2CD@microsoft.com...
    > NICE!
    > Thank you so very much.
    >
    >
    > "strive4peace" wrote:
    >
    >> Hi John,
    >>
    >> if you are using code to execute the query, use
    >>
    >> currentdb.execute "QueryName"
    >>
    >> instead of
    >>
    >> DoCmd.OpenQuery "QueryName"
    >>
    >> ~~~~~~~~~~~~~~~~~~~~~~~~~
    >>
    >> if you are using macros or just opening queries from the database
    >> window, before you run action queries:
    >>
    >> macro action --> SetWarnings --> false
    >> macro action --> Echo --> false
    >>
    >> then, after you run action queries...
    >>
    >> macro action --> Echo --> true
    >> macro action --> SetWarnings --> true
    >>
    >> Warm Regards,
    >> Crystal
    >> *
    >> :) have an awesome day :)
    >> *
    >> MVP Access
    >> Remote programming and Training
    >> strive4peace2006 at yahoo.com
    >> *
    >>
    >>
    >>
    >> John In Palmer wrote:
    >> > Hi all,
    >> > Can anyone tell me how to get rid of the annoying messages that pop up
    >> > from
    >> > within Access when attempting to run an update or delete query? I would
    >> > like
    >> > to have the ability to bypass those messages. Thank you in advance.

    >>
     
  6. strive4peace

    strive4peace
    Expand Collapse
    Guest

    You're welcome, John ;) happy to help

    Warm Regards,
    Crystal
    *
    :) have an awesome day :)
    *
    MVP Access
    Remote programming and Training
    strive4peace2006 at yahoo.com
    *



    John In Palmer wrote:
    > NICE!
    > Thank you so very much.
    >
    >
    > "strive4peace" wrote:
    >
    >> Hi John,
    >>
    >> if you are using code to execute the query, use
    >>
    >> currentdb.execute "QueryName"
    >>
    >> instead of
    >>
    >> DoCmd.OpenQuery "QueryName"
    >>
    >> ~~~~~~~~~~~~~~~~~~~~~~~~~
    >>
    >> if you are using macros or just opening queries from the database
    >> window, before you run action queries:
    >>
    >> macro action --> SetWarnings --> false
    >> macro action --> Echo --> false
    >>
    >> then, after you run action queries...
    >>
    >> macro action --> Echo --> true
    >> macro action --> SetWarnings --> true
    >>
    >> Warm Regards,
    >> Crystal
    >> *
    >> :) have an awesome day :)
    >> *
    >> MVP Access
    >> Remote programming and Training
    >> strive4peace2006 at yahoo.com
    >> *
    >>
    >>
    >>
    >> John In Palmer wrote:
    >>> Hi all,
    >>> Can anyone tell me how to get rid of the annoying messages that pop up from
    >>> within Access when attempting to run an update or delete query? I would like
    >>> to have the ability to bypass those messages. Thank you in advance.
     
  7. strive4peace

    strive4peace
    Expand Collapse
    Guest

    nice link, thanks Allen!

    Warm Regards,
    Crystal
    *
    :) have an awesome day :)
    *
    MVP Access
    Remote programming and Training
    strive4peace2006 at yahoo.com
    *



    Allen Browne wrote:
    > Crystal has already answered your question, but if you want more detail see:
    > Action queries: suppressing dialogs, while knowing results
    > at:
    > http://allenbrowne.com/ser-60.html
    >
     
  8. Tony Toews

    Tony Toews
    Expand Collapse
    Guest

    strive4peace <strive4peace2006@yahoo.com> wrote:

    >if you are using code to execute the query, use
    >currentdb.execute "QueryName"


    Currentedb.execute "QueryName", dbfailonerrors is highly recommended
    so you see any error messages.

    Tony
    --
    Tony Toews, Microsoft Access MVP
    Please respond only in the newsgroups so that others can
    read the entire thread of messages.
    Microsoft Access Links, Hints, Tips & Accounting Systems at
    http://www.granite.ab.ca/accsmstr.htm
     
  9. strive4peace

    strive4peace
    Expand Collapse
    Guest

    Re: Update query notifications -- dbFailOnError

    thanks, Tony!

    sometimes I leave off parameters to keep it simple, but using
    dbFailOnError is a good idea ... especially if there is no error handler

    Warm Regards,
    Crystal
    *
    :) have an awesome day :)
    *
    MVP Access
    Remote programming and Training
    strive4peace2006 at yahoo.com
    *



    Tony Toews wrote:
    > strive4peace <strive4peace2006@yahoo.com> wrote:
    >
    >> if you are using code to execute the query, use
    >> currentdb.execute "QueryName"

    >
    > Currentedb.execute "QueryName", dbfailonerrors is highly recommended
    > so you see any error messages.
    >
    > Tony
     
  10. John In Palmer

    John In Palmer
    Expand Collapse
    Guest

    Re: Update query notifications -- dbFailOnError

    Thanks to Crystal, Allen and Tony for some excellent information. You guys
    are great.

    "strive4peace" wrote:

    > thanks, Tony!
    >
    > sometimes I leave off parameters to keep it simple, but using
    > dbFailOnError is a good idea ... especially if there is no error handler
    >
    > Warm Regards,
    > Crystal
    > *
    > :) have an awesome day :)
    > *
    > MVP Access
    > Remote programming and Training
    > strive4peace2006 at yahoo.com
    > *
    >
    >
    >
    > Tony Toews wrote:
    > > strive4peace <strive4peace2006@yahoo.com> wrote:
    > >
    > >> if you are using code to execute the query, use
    > >> currentdb.execute "QueryName"

    > >
    > > Currentedb.execute "QueryName", dbfailonerrors is highly recommended
    > > so you see any error messages.
    > >
    > > Tony

    >
     
  11. strive4peace

    strive4peace
    Expand Collapse
    Guest

    Re: Update query notifications -- dbFailOnError

    you're welcome, John ;) happy to help

    Warm Regards,
    Crystal
    *
    :) have an awesome day :)
    *
    MVP Access
    Remote programming and Training
    strive4peace2006 at yahoo.com
    *



    John In Palmer wrote:
    > Thanks to Crystal, Allen and Tony for some excellent information. You guys
    > are great.
    >
    > "strive4peace" wrote:
    >
    >> thanks, Tony!
    >>
    >> sometimes I leave off parameters to keep it simple, but using
    >> dbFailOnError is a good idea ... especially if there is no error handler
    >>
    >> Warm Regards,
    >> Crystal
    >> *
    >> :) have an awesome day :)
    >> *
    >> MVP Access
    >> Remote programming and Training
    >> strive4peace2006 at yahoo.com
    >> *
    >>
    >>
    >>
    >> Tony Toews wrote:
    >>> strive4peace <strive4peace2006@yahoo.com> wrote:
    >>>
    >>>> if you are using code to execute the query, use
    >>>> currentdb.execute "QueryName"
    >>> Currentedb.execute "QueryName", dbfailonerrors is highly recommended
    >>> so you see any error messages.
    >>>
    >>> Tony
     

Share This Page