How to check when a VBA module was modified?
<p>I have written a version control module.  The AutoExec macro launches it whenever I, or one of the other maintainers log in.  It looks for database objects that have been created or modified since the previous update, and then adds an entry to the Versions table and then opens the table (filtered to the last record) so I can type in a summary of the changes I performed.  </p>

<p>It is working great for Tables, Queries, Forms, Macros, etc but I cannot get it to work correctly for modules.</p>

<p>I have found two different properties that suggest a Last Modified date ...</p>

<pre><code>CurrentDB.Containers("Modules").Documents("MyModule").Properties("LastUpdated").Value
CurrentProject.AllModules("MyModule").DateModified
</code></pre>

<p>The first one (CurrentDB) always shows "LastUpdated" as the Date it was created, unless you modify the description of the module or something in the interface.  This tells me that this property is purely for the container object - not what's in it.</p>

<p>The second one works a lot better.  It accurately shows the date when I modify and compile/save the module.   The only problem is that when you save or compile a module, it saves / compiles ALL the modules again, and therefore sets the DateModified field to the same date across the board.  It kind of defeats the purpose of having the DateModified property on the individual modules doesn't it?</p>

<p>So my next course of action is going to a bit more drastic.  I am thinking I will need to maintain a list of all the modules, and count the lines of code in each module using VBA Extensions.  Then, if the lines of code differs from what the list has recorded - then I know that the module has been modified - I just won't know when, other than "since the last time I checked"</p>

<p>Does anyone have a better approach?  I'd rather not do my next course of action because I can see it noticeably affecting database performance (in the bad kind of way)</p>