Simple vbYesNo problem

[Tuckejam]

It appears I have lost my mind, or at lease what little coding knowledge I thought I had learned.



I have a form with records and want a simple warning when deleting a record.

when using the code below, the no button deletes a record, and the yes button appears to do nothing except if you click yes then no, it deletes 2 records ??

 Private Sub Form_Delete(Cancel As Integer)   If MsgBox(" Are you sure you want to delete this record? ", vbYesNo) = vbYes Then
         Me.AllowDeletions = True
         DoCmd.RunCommand acCmdDeleteRecord
         Me.AllowDeletions = False
      Else
         Exit Sub
    End If
End Sub

thanks for the help

[davegri]

Add line
Me.Requery
just before the Else

[moke123]

Is the OnDelete event the event to use?
There's a reason for the cancel arguement.
Its not clear how you are invoking the delete.

I would use an OnClick event of a command button with your code.

I've never used the OnDelete event but I would imagine you would do something like

Private Sub Form_Delete(Cancel As Integer) 

If MsgBox(" Are you sure you want to delete this record? ", vbYesNo) = vbNo Then 

         cancel = true

    End If

End Sub

[Micron]

The code is wrong for the event IMO. User deletes, record moves into a buffer, event runs and if you click no you've already deleted anyway. Yes should cause you run a delete command on the next record (which has now become the current record) because of the way you've coded it. If using this event, I believe you simply cancel or not, which restores the record, or not.

[Welshgasman]

Why not use a relevant event?
https://docs.microsoft.com/en-us/off...lconfirm(even)

[moke123]

Thats another event I've never used or had a use for, or even looked at before.
now I've noticed a "before screen tip" event. I think I'll be googling for a while.

[Welshgasman]

Thats another event I've never used or had a use for, or even looked at before.
now I've noticed a "before screen tip" event. I think I'll be googling for a while.

I think I might have used it once.

Found it

Private Sub Form_AfterDelConfirm(Status As Integer)
 Select Case Status
    Case acDeleteOK
        MsgBox "Record deleted!", , "Delete Result"
    Case acDeleteCancel
        MsgBox "Delete record cancelled!", , "Delete Result"
    Case acDeleteUserCancel
        MsgBox "Delete record cancelled!", , "Delete Result"
 End Select
End Sub

Private Sub Form_BeforeDelConfirm(Cancel As Integer, Response As Integer)
Response = acDataErrContinue
 ' Display custom dialog box.
If MsgBox("Are you sure you want to delete this record?", vbYesNo, "Delete Confirmation") = vbNo Then
    Cancel = True
End If
End Sub

[Missinglinq]

 Private Sub Form_Delete(Cancel As Integer)   
   If MsgBox(" Are you sure you want to delete this record? ", vbYesNo) = vbYes Then
         Me.AllowDeletions = True
         DoCmd.RunCommand acCmdDeleteRecord
         Me.AllowDeletions = False
   Else
         Exit Sub
   End If
End Sub

I agree that another event should be used here...but what I'm really confused about is your code and scenario...as presented.

The line

Me.AllowDeletions = True

would indicate that you have AllowDeletions set to No/False elsewhere...either in code or in the Properties Pane. If this is true (is it?) how would you get to the Form_Delete event in the first place? IF this is a false assumption, why have Me.AllowDeletions = True at all?

Linq ;0)>