Unless your colleagues configure their Word installations to allow trusted access to the VBA project model - something that is dangerous to have as a default state - your scheme won't work.



Instead, if your updating code that belongs in a template they're to use, simply roll out the new template, preferably by having the users concerned joined to a group whose group templates folder is one you can update. That way, they don't have to do anything.

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Hi Paul,

So about half of my code is held in a group folder that I can update there, so that's good... Unfortunately, the other half is held within userforms that really needs to be updated within their STARTUP folders.

I figured that by using a prompt in a userform that they initiate themselves (by actually going to macros -> view -> run, not using Auto_Open) I'd be able to give whatever privileges are needed to make the update - Is this not possible?

Worst come to worst, I'd figure I can at least have the code close out of Microsoft Word and open the folder containing the "newcode.dotm", so all they'd have to do is copy it and drag it to their STARTUP folder again. Do you think this is the best, tangible solution?

Perhaps the code can open 2 folders side by side, one containing the new code, the other containing the STARTUP folder, so all they have to do is drag and drop?