Unable to pull back delete record

[b.saimsc]

Hi all,

I have problem in my form. I have kept two command button 1 is for delete record it's works fine & another one is Undo record but it's not working.
For Delete Record:

Private Sub Command_Click()


DoCmd.RunCommand acCmdDeleteRecord
End Sub
It's working........................

For Undo:

Private Sub Command2_Click()
Me.Undo
End Sub

Undo is not working please help me

Thanks in advance

[June7]

You want to undo record deletion? Can't Undo record deletion. Once it's gone, it's gone.

Undo should work only to undo edits of record.

[b.saimsc]

Undo record Deletion can't work in Access?

[June7]

Can't undo record deletion. Record deleted is gone. That's why there is a warning message when deleting with the keyboard Delete key.

[alcapps]

If that is something that you want too do is keep deleted records?
you can do it by faking a deletion, in other words you have your normal table but add a yes no or date field your choice. You handle the deletes manually by marking them deleted setting the date or y for deleted. In your normal forms data source you have too filter for n or null deleted record fields. Very manual process but it keeps records forever or until someone accidentally runs a delete query.

[June7]

Good advice Al. Deleting can be an issue if there are relationships. Instead have a field to set record status. Such as 'Closed' or 'Pending', etc. or a DateClosed field. Then apply filter.

So b, why do you want to allow record deletion? This should be a rare event in a relational database.

[tmd63]

You could try transactional process instead. There you can delete any number of files and they will be held in limbo until to complete the transaction.
I used it for a very large MRPII database with multiple users. The transactions were used to move stock from the instock database container to a work-in-progress database container. If I did this on a per item method, someone could delete or process a similar item at the same time. But with transactional processes, the whole was not moved until the final 'commit' action was performed.

[Missinglinq]

The advice given by alcapps and June7 is pretty much the standard approach used by experienced Access developers vis-à-vis 'deleting' Records. It allows for the retention/availability of historic Records, more and more a requirement in today's world of 'everything is on computer,' as well as the easy retrieval of Records that were accidentally deleted, as in your scenario.

Linq ;0)>