In case anyone is searching this form looking for ideas on how to accomplish this, here is what I do to ensure that everyone is running the latest code (this code is being used in Excel).
Create a simple Excel Addin that has code to load a module into vba from a standard location (I have it at a shared network folder). The Addin should never change, and therefore is suitable for everyone to load on their copy of Excel. Here is the code I have for the AddIn that I wrote. It resides in the "ThisWorkbook" section:
Private Sub app_WorkbookActivate(ByVal Wb As Workbook)
'Register the ###### Macros
Debug.Print "Registering ###### Macros"
Call RegisterMacros
End Sub
Private Sub Workbook_Open()
On Error Resume Next
Application.EnableEvents = True
Set app = Application
'Remove ######Functions
Set mf = Application.VBE.VBProjects("*your addin name*").VBComponents.Item("*your module file name*")
Application.VBE.VBProjects("*your addin name*").VBComponents.Item("*your module file name*").Name = "*your module file name*remove"
Application.VBE.VBProjects("*your addin name*").VBComponents.Remove mf
'Add ######Functions from network
Application.VBE.VBProjects("*your addin name*").VBComponents.Import "*your file location here\*your module file name*.bas"
End Sub
With this code, whenever a Excel is opened, it renames and removes the module (if it exists). It then imports the module into VBA. The app_WorkbookActivate event calls a function that I have in my module that registers all the macros I wrote with Excel (so that all of the User Defined Functions aren't stored under "UserFunctions", and instead stored in custom folders).
It's all really simple, but it has worked for me for the last 10 years. The only thing to remember with this is that if you make any changes to your module, and you save it, you need to "export" the module. If you don't, your saved changes will be overwritten with the saved module the next time Excel is started.