Implementation of VbaProject.OTM

Finally, there are some elements for deploying Outlook VBA Project. There are many ways to do this, but the easiest way to do it without installing anything and following the same methodology is to run the OTM file directly from the server. I found out that the outlook.exe process has an altvba parameter that allows you to specify a different path to launch the OTM file. Here's an example:

outlook.exe /altvba "\\myServer\myFolder\myFile.otm"

This only allows me to update one file to update all computers. Obviously, if the file is large and the server ping is on the high side, it may delay Outlook starting. Another problem with this method is that everyone will have to turn off Office if you want to update the OTM file on the server (and if you work in an office where everyone is using Outlook, you know this is not possibleto force everyone to close it at the same time, unless you coded a macro at the end of the code). To prevent both of these problems, I could configure the batch file to copy the OTM server client files every time there is a new version (just need to check the last-modify NTFS attribute). This way Outlook will download with the local file, the batch file will take 2-3 seconds to copy the file if needed (or start Outlook instantly), and there is no problem updating the OTM file on the server. Users will have to launch Outlook with a batch file (or with a slightly different outlook.exe appearance with an altvba parameter, so they need the first shortcut / file to launch them anyway). Another advantagealtvba

is that it is easy for the user to start Outlook without it (to see if VBA is problematic or not if Outlook is sluggish) and after reinitializing Outlook, the file will remain unchanged.

Other solutions include a COM add-in, which can be developed in many languages ​​including VB6 (no conversion from VBA). Microsoft Office XP Developer also has many tools to help you get the job done (but not free, especially if you want the most up-to-date version).