Follow Duanes advice.
There are procedures in rthese fora / faqs (see Transaction Log for Ms. Access" in the faq section.) illustrating the generation / creation of audit trails. They are not -particularly for MS Access- foolproof, but are workable for the general user community of MS Access users.
Given the appropiate audit trail of changes to records, does not, however, make the job of reporting the changes either easy or even practical. Since a true 'audit trail' will extend from it's inception to the time of use, you need to delimit the listing of the audits in some manner.
Maiintaining the audit trail itself is an issue, as in the typical active database, hte audit trail will be one of the most rapidly growing recordsets in the database. To keep track of who made what change - and when they made it requires that each change be recorded at the table and field level along with the username and date-time stamp of the change. Further, please note that in an MS Access application (with the Jet db engine). The only changes which can be captured are tose made via Forms. Queries and manual edits of the database do not generate events which permit the capture of data changes. thus a first step is to basically deny access to any objects except forms to the entire user community. Also, note that design changes are not subject to capture in any autonomus manner.
If you proceed with the development of the report (including its pre-requsits), I would be somewhat interested in following the development process and seeing the finished project.
MichaelRed