Word VBA (XP)

Topic

New Reply

any other addins installed? winfax and acrobat are two that can cvause problems…

Reply | Quote

Replies

My posted problems appear to have been solved by any or all of reducing the macro security level from high to medium and unchecking, under
Templates and Add-Ins, all loaded items: EWED.DOT, WWEBVB.DOT, FileNew.dot, FloppyCopy.dot, and Selection Word Count.dot.

Reply | Quote

it’s safer to use high security and sign the macros. use selfcert or an email digital signature for personal use.

Reply | Quote

I can’t install WOPR 2000 (and don’t know if it’s advisable) because it can’t find the correct version of WinWord. I still have remnants from the previous installation.

Reply | Quote

Everything I’ve heard about digitally signing your macros is more trouble than it’s worth. The last I heard, Verisign would no longer give digital certificates to single developers. In a corporate/business environment getting Microsoft’s Certificate Server up and running is more painful than sticking bamboo up your fingernails, and getting a corporate digital certificate is very expensive. What are the alternatives for someone who develops Office VBA solutions for internal corporate use? Having everyone set their macro security to medium? Installing your macros in the back door startup folder?

Any ideas would be appreciated.

Reply | Quote

you can use an email signature or selfcert. i use the one i use for email, waiting to sign it after i’m done completely and ready to roll it out to other machines.

i find it’s easier (takes seconds) than approving macros all the time – and i don’t risk being confused and approving the wrong one.

Reply | Quote

Peter,

I don’t have XP so haven’t been checking this forum – anyway: the compile error message will have to do with the code in one of the add-ins and is not a security issue per se. So it’s virtually certain that unloading the add-ins is what made the problem go away.

To determine which of these add-ins contains the non-compiling code, you could try temporarily moving all of them out of the Startup folder, and then moving them back in one at a time, and each time starting Word to see which one is triggering the message.

Gary

Reply | Quote

Word reports Compile error in hidden modules FileNew, FileSaveAs, and modShadowMacros. WOPR, Avery Wizard, and WordWeb were uninstalled and Normal.dot was deleted before installation, and installation has been repeated several times over. I prefer not to have to reformat the disk.

Reply | Quote