I think, Jason's idea is the simplest one. When I press delete button, I can store recno() in a cursor. Then in form's release method I can check for these records, if the record is deleted, delete files. Seems like a cheap and easy solution. I don't see downsides at the moment. Do you?

>When I said "and store this new file name in a field in your file manager." I was attempting to address this issue. The lack of a PK is certainly a hurdle. There could be a new table that only has deleted records in it--it would have original file name (with full path, I suppose), and the new file name in the TrashCan. With no PK, there has to be something unique to identify each entry...
>
>And I like Ed's idea of compressing the trashCan (I think he is suggesting a longer term archive).
>
>>
>>But the first question still remains - how would I know, which records were "deleted" and "reverted". Should I create some array (cursor) on record numbers [Table doesn't have PK - ouch] and populate this array (storage) in delete command [Save/TableRevert would empty this storage]?