Close or Unload

[salvelinus]

Which event is the best place to put code that should be run when the user closes a form? I have code in the Unload event of a form that is supposed to send an email and delete all data from a table. It's always worked for two users, but not for a new user. I'm not sure what she did differently. The way they close the form is to click the x button in the control box.
Is there a reason the code should be in the close event rather than the unload event? I've typically used the close event just to check if the user really wants to close the form.
Thanks.

[RobDog888]

The Form_Unload event would be the better event to trap for canceling of
the form from unloading if a user wants to change their mind.

The Close event occurs after the Unload event, which is triggered after the form is closed but before it is
removed from the screen. When you close a form, the following events occur in this order:

Unload → Deactivate → Close

When the Close event occurs, you can open another window or request the user's name to make a log entry
indicating who used the form or report.

The Unload event can be canceled, but the Close event can't.

HTH

[salvelinus]

Ok, thanks, I guess I got the verifying the close mixed up. Haven't actually checked for that in a long time.
But in the code below, ClearTempLog is a sub that deletes all data from the TempLog table, and it didn't run. That's what I can't figure out.

If MsgBox("Are you finished editing the " & mstrDbName & " comments?", vbYesNo + vbQuestion, "Editing Complete?") = vbYes Then
            DoCmd.SendObject acSendTable, mstrLogName, acFormatTXT, "Boss", , , mstrDbName & _
            " Editor Changes", mstrDbName & " changes attached.", True
            ClearTempLog
        End If

[RobDog888]

Place a breakpoint at the If MsgBox line. Then run your form and close it answering it with yes. Step
through and see where the code execution is going. Is it evaluating the vbYes? Is it going into the
ClearTempLog procedure but generating an error so it jumps out of that procd?