learn a well known and effective developer methodology - take backups before any changes, document your code where changes are made and keep a detailed log of changes - who, when, why, what, where
I back up each file that I use at least once a day (before I open the file) regardless of whether I make changes, just in case something happens - that is how I found the earlier report.
I document changes in vba, just haven't figured out the best way for me to document non vba changes such as moving or adding a textbox to a report and determining how often/significant a change should qualify for such documentation since some changes such as moving a text box over a quarter inch or changing point size from 9 to 8. Otherwise end up spending too much time on putting together a list of too many changes. Then also the issue of documenting inside the file as a table or outside in a text or excel file.
for mentioning the database documenter. I'll take a look and see if that sheds any light. I think the report in question is ok from standpoint of not being changed as it is a fairly simple report having only two text boxes.