One of my projects had a revision-history requirement as a table rather than as comment-style text. The displayed version on the opening form was based on the revision entry with the latest, greatest date.
The record was something like
tblRevHist
EntNum, autonumber (PK)
EntDate, date of change
EntPers, text(3), the initials of the person making the change
EntVers, text(8), the formal version nnn.nn-x
EntObjTyp, text(1), a code for what object was modified for this entry, which was something like T=table, Q=query, F=form, R=report, G=general module, C=class module, M=macro, L=relationship, and we didn't have ADP in this so never had any pages to change - but P was available if we needed it.
EntObjNam, text(32), the name of the object changed
EntChange, Memo, the nature of the change.
EntDate and EntVers were indexed, dups allowed.
The rules in place at the time were that if I changed an object, I entered something for EntChange, but the version didn't have to change from one entry to the next if I had changed several objects at once.
We also had another table that recorded suggestions on the configuration and one of the fields in that table matched version numbers if we ever actually implemented the suggested change.
Perhaps you meant something more like this.