Re: Delete/Update prompts
- From: "David C. Holley" <DavidCHolley@xxxxxxxxxxxx>
- Date: Mon, 18 Apr 2005 23:30:30 -0400
Well yeah, but currently all my stuff is for myself (I'm self-employed.)
David H (VERY LONG several days)
Mark M wrote:
I used to do this too. But what happens if the query pukes and causes an error where you're presented with the good ol' "Debug or End" prompt? It would be good to have some basic error handling in place to set the warnings back to true in the event of an error. But, I'm sure we all have at least some rudimentary error-handlers in each procedure. :-)
"David C. Holley" <DavidCHolley@xxxxxxxxxxxx> wrote in message news:OtgahzGRFHA.2356@xxxxxxxxxxxxxxxxxxxxxxx
DoCmd.SetWarnings False DoCmd.RunSQL (or DoCmd.OpenQuery) DoCmd.SetWarnings True
I'm in the habit of encapsulating the query to ensure that the warnings are always turned back on afterward as there are times that I want to see them, esp If I'm developing something or if theres the possibility that the user may run a query.
Jim wrote:
I have sql in vba that does update and deletes..when they trigger a prompt asking the user if they want to delete/update the table appears...How can I stop that from happening and just have the statement go through?
thanks
.
- References:
- Delete/Update prompts
- From: Jim
- Re: Delete/Update prompts
- From: David C. Holley
- Delete/Update prompts
- Prev by Date: Re: How to create a right-click "add then paste" menu item instead of just paste
- Next by Date: Re: Cycle through controls to assign Source
- Previous by thread: Re: Delete/Update prompts
- Next by thread: Pbm writing to record
- Index(es):
Relevant Pages
|