Hello,

So.... I've been working on this project where I have 2 userForms and 1 module... all of which contain macros/subs/functions inside of them. I have been doing this all under the Normal.dotm file.

At this point, I have gotten everything functional and happy with the results. However, from my readings online I have found that it is definitely not a good idea to have all of these items tied to the Normal.dotm file since other people in my group need access to these and I don't want to mistakenly erase unrelated things they may have in their own normal.dotm file.

With that being said, I did some reading and decided to create my own dotm file and have it reside on the startup folder for word. so myTest.dotm has the modules and userforms I exported from my normal.dotm file attached to it. It is saved in the startup folder. I have verified that this part is correct because if i launch a new word instance I can see that it recognizes these macros under the myTest.dotm file in run macros tool.

The problem comes when I try to run any of these macros though. I get:

Compile error in hidden module: protectMacros.
This eeor commonly occurs when code is incompatible with the version, platform, or architecture of this application. Click 'Help' for information on how to correct this error.

So what am I doing wrong? All of these items worked perfectly when in the normal.dotm file. All i did was export them from normal.dotm and imported them into myTest.dotm. I deleted them from normal.dotm. I added myTest.dotm to my startup


folder for word.

edit: I ensured that none of my code made reference to things like call normal.protectMacros.verify to which I changed it to call myTest.protectMacros.verify

Please help. Thanks.

Well... some of it maybe solved.... when I created the new global template, I didn't include the same references that my normal.dotm had on it. I have added those, and I have now been able to get farther into the application before. I did receive the same error message pertaining to a different module than before though. This leads me to believe that I may have an issue with normal.yadada still residing somewhere inside that module, which I will look into.....

yup, including references on my global template was the issue. problem solved. thanks for viewing!