[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1371
  • Last Modified:

How to suppress the Delete Confirm dialog box when using SQL statement to delete record

I'm using an SQL delete statement to delete a contact from a table. I used the following code to suppress the dialog box but it's not working:

Private Sub Form_BeforeDelConfirm(Cancel As Integer, _
                                  Response As Integer)
    ' Suppress default Delete Confirm dialog box.
    Response = acDataErrContinue     ' Display custom dialog box.
    If MsgBox("Delete this record?", vbOKCancel) = vbCancel Then
        Cancel = True    
    End If
End Sub

This is just the code from Visual Basic Help. What could be wrong? Thanks.
0
cindyrod
Asked:
cindyrod
  • 6
  • 6
  • 5
2 Solutions
 
walterecookCommented:
if you use
docmd.setwarnings false

that turns off the confirm

Walt
0
 
walterecookCommented:
don't forget to turn it back on
docmd.set warnings true

or if you use the execute command, that in itself suppresses the message

currentdb.execute "Some SQL here"

Good luck
Walt
0
 
walterecookCommented:
so either:
docmd.setwarnings false
docmd.openquery "Some deletequery"
docmd.setwarnings true

or
currentdb.execute "DELETE * FROM...."

You won't need the deleteConfirm code

Walt
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Steve BinkCommented:
If you would like to eliminate the warning dialogs permanently, look in [Tools | Options] under the "Edit/Find" tab.  There are three confirmation dialogs you can disable.  Be warned, though...this disables those dialogs in Access, not just the current db.  
0
 
cindyrodAuthor Commented:
Why isn't the BeforeDelConfirm working? Any ideas?
0
 
walterecookCommented:
Well Cindy,
we're telling you that you don't even need beforeDelConfirm.
0
 
cindyrodAuthor Commented:
I know, I just want to know why it didn't work.
0
 
walterecookCommented:
This suppresses the Access system message:
Response = acDataErrContinue

No matter what this line is going to fire:

 If MsgBox("Delete this record?", vbOKCancel)

the cancel = true prevents the query from running.

Make sense?

Walt
0
 
cindyrodAuthor Commented:
But why is the system message still showing up if I use that code?
0
 
walterecookCommented:
So you get 2 prompts?

0
 
Steve BinkCommented:
Have you placed a breakpoint in your code to ensure the event is firing?  Try rebuilding the individual event by deleting the code you have now, selecting the same event from the drop-downs at the top of the code window, and re-enter the code.  Any change?  Try using this code on a copy (this SHOULD delete records with no warnings) and see if it still shows up:

Private Sub Form_BeforeDelConfirm(Cancel as Integer, Response as Integer)

Cancel = 0
Response = 0

End Sub
0
 
cindyrodAuthor Commented:
Actually, I only get the Access prompt (the default one). I guess that the event is not even firing. Is this because the deletion is done through SQL statement (DoCmd.RunSQL deleteStatement)?
0
 
Steve BinkCommented:
LOL!  Yeah, that's it.  The form's event will only fire when you act on the form's recordset.  Executing a separate DELETE query by using DoCmd.RunSQL or CurrentDB.Execute will not trigger the event.
0
 
cindyrodAuthor Commented:
Oh, I see. That makes sense. So the only way to suppress this message in my form is by setting the warning to false or using the currendDB.Execute method? Which way is more efficient? Does turning off the warnings suppress other important messages such as runtime errors and errors found during deletion/insertion/update?

Thank you both for your great help.
0
 
Steve BinkCommented:
CurrentDB.Execute is generally the preferred method, though suppressing the warning messages with the SetWarnings method only applies to DoCmd.RunSQL.  The CurrentDB method has other methods of error-checking and result reporting.

Turning off the warnings will only suppress WARNINGS regarding your data manipulation.  For example, if you have Table1 with 2 fields (f1 number, f2 required text, no blank values) and run this statement:

DoCmd.RunSQL "INSERT INTO Table1 (f1,f2) VALUES (1,'');"

Access will pop up the warning regarding a violation of validation rules.  If you first run this line:

DoCmd.SetWarnings False

Access will not pop up the warning window, but it will also not INSERT the values requested.  If the warning window is allowed to come up, and the user opts to NOT run the query for whatever reason, a run-time error will be generated (error 2501: RunSQL action was canceled).  Suppressing the window will not generate an error (other than for SQL syntax), but it will not complete any 'invalid' queries, nor will it alert you to this fact.
0
 
cindyrodAuthor Commented:
If I use CurrentDB.Execute, then I will still get the error messages regarding validation rules,etc.? I just want to suppress messages like "You are going to delete ...", "You are going to append ...", etc., not messages about Runtime errors, violation of primary keys, etc.
0
 
Steve BinkCommented:
CurrentDB.Execute will not generate ANY message boxes regarding the transaction/statement you send to it.  It does, however, provide for returning the number of records affected by the last query.  The only error messages it will generate are syntax errors and functionality issues (e.g., requesting functionality the drivers do not support).  For validation rule violations, PK/FK violations, and data-typing, you will not see an error.  Below is an example of how you would use the RecordsAffected property to find a problem:

set db = currentdb
set rs = db.openrecordset("SELECT * FROM MyTable")
rs.movelast
x = rs.recordcount
rs.close

db.execute "INSERT INTO MyTable2 (f1,f2,f3) SELECT * FROM MyTable"
if db.recordsaffected <> x then msgbox "Records available and records inserted did not match."
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 6
  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now