On new record, abandon record before it is saved?

[Seth Schrock]

I've got a way for the user to delete the record. The user just didn't know it. I might end up putting a Delete button next to the Undo button so that they can find it easier.

An idea just occurred to me. If a user starts typing a new record and decides they don't want a new record, is it possible to delete the record before it is saved? If so, then I could just replace my Undo button with a Delete button that will work as both my Undo and Delete button. I know the functions are totally different, but in this case, the Undo wasn't to undo changes to an existing record, but to stop the creation of a new record if the user found out that the order had already been inputted.

[zmbd]

New question new thread.
I hope the title works. :)

User can hit [Esc] key.
In either before_insert or before_update event of the form the set cancel = true : me.undo - I have a form that does just that in the before insert event. The only issue is that the autonumber field increments even though the user canceled the record save.

I know I'm missing something here; however, I'm just a tad scattered today with the Holidays and current family events

Anyway here's one I use in the before insert:

IF the answer is [No] the new record isn't inserted and the autonumber doesn't increment either.

Private Sub Form_BeforeInsert(Cancel As Integer)
Dim zvbyesno As Long
'
    zvbyesno = fnc_msg_confirm_action_defaultNo("This is a real time change! Before Insert..." & vbCrLf & "This can not be undone once confirmed!")
    If zvbyesno = vbNo Then
        Cancel = True
        Call sub_msg_action_canceled
        Me.Undo
    End If
End Sub

I use basically the same code in the before_update, if the answer is [No] then the record is aborted; however, the autonumber in the table is incremented.

(line 4, I have a series of the same message boxes some with yes/no or yes/no/cancel, different default buttons icons, one day I put them all in a standard module as functions or subs if I didn't need a return, and then I just pass the header message text)

[NeoPa]

Forms have two properties that might prove helpful with this logic Seth - .NewRecord and .Dirty.

.NewRecord tells the code that the buffer is currently loaded with data for a new record, and .Dirty tells the code that changes have been made to data in the buffer.

No deletes need (or even can) be performed on a record until it has been saved the first time at least, as it isn't stored in the table until that point.

With this information you can use code triggered by a button.

[Seth Schrock]

Okay. Sorry I wasn't able to get back sooner. I got pulled away to another task.

I really don't care about the autonumber being incremented, so I'll just stick with the simple method and keep what I've got in the Undo button and just add a delete button.

Thanks Z and NeoPa for your help.