I've never had a VBA capable notebook.
Expect to get one early next year, so I have been thinking about the implications for VBA code security. This caused me to do the following.
1. I split my gloabal utilities template into two pieces. One piece has little more than the code for my toolbars and menus, call this Utilities-1. The other has the rest.
2. I convertered ALL the code in Utilities-1 to VB 6 and compiled an ActiveX DLL. So there is now, in effect NO code in Utilities-1.dot. Just code of the form:
[VBA] Public Sub HKCreateToolBar()
clsWordVB1.HKCreateToolBar
End Sub
[/VBA]
This protects all the code in HKCreateToolbar from prying eyes.
3. I just finished a similar effort for the code in the Normal template.
So, if somebody prys in, or steals, my notebook, at least they cannot see my source code.
Note that most of the code was easy to convert to a VB DLL, but some was not so simple. I had eased the task because I already had VB 6 Forms for some code that also was already running in VB 6.
I could carry the VB 6 source separately on a CD, or I could be really paranoid and not even have the source with me when I travel. Worst case is I have to tolerate Word's default's until I get home. I will travel with only essential source code.