I have answered my own question! The to-be-deleted database record has not yet been deleted when the data macro's AfterDelete event fires. What was leading me astray was that I'm used to the Access VBA form events (BeforeDelete, BeforeDelConfirm, and AfterDelConfirm). Unlike the form events where the to-be-deleted record is moved to a temporary buffer, the data macro AfterDelete event still has visibility to the to-be-deleted record (the record is deleted after this event is complete).

The AfterDelete data macro event has a full compliment of macro commands, like the BeforeInsert and BeforeUpdate events -- including the RunDataMacro command. So I am able to capture the to-be-delete table record's fields in an audit trail.

Problem solved...