Create Version Tracking for keeping users on the same version


While not automatic, this is how I do version tracking:

Create a local table called TblLocalRevision:

Make the RevisionNum and RevNotes fields set to Append Only  –  YES:

Enter data in the table to create ONE row only – with ID 1.

Enter data in Version nuber ex. 2.3   and notes ex.: Added a logo to the menu and added new sales report.

Show the current version number in your database using a dlookup on an unbound field in any form:


Now, anytime you push out a new updated front end, the latest version number shows.  If you make changes, do NOT add a new line.  Simply update the existing Version and Notes to whatever you want.  Because it is set to Append Only, it will archive the changes in that one row.  Now you can see the history by right clicking the field and choosing Show History.  Your user will always be able to see what version they are on.  Because it is a local table, you can push out updated front ends and users know if they have the latest version or not.

Simple, but effective.  YES, you can automate this with scripts or policies or other mehods – I have done that.  But that is a different lesson!

Related Posts

Access 2016 Relationships

Short blog today, this is a great read on relationships in Access 2016: Access 2016 Relationships Thanks to Microsoft for this one!

Microsoft Access Union Query from Hell. Skill Level: Demi-God

The worst query I ever had to write which powers a master report for the database user.  Here it is.  I don't think I can make it smaller, there were too many weird rules, aggregates, and translations in it.  And we needed to pull different columns based on criteria. ...



Submit a Comment