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)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007