Macro Security Setting (2002/SR2)

**curious** · 2006-09-09 19:25

Edited by HansV to create link to MSKB article

Hi -

Have been receiving message

**HansV** · 2006-09-09 19:28

Try Phil Rabichow's <!post=Systematic Approach to Behavioral Problems in Word (97/2000),197827>Systematic Approach to Behavioral Problems in Word (97/2000)<!/post>.

**jscher2000** · 2006-09-10 04:45

> I simply copy the macro, delete it, and paste it back.

I don't understand your scenario. Word starts up normally, then you run a macro and get an error, then you edit the macro and it runs fine?

**curious** · 2006-09-10 17:23

Yup.

**jscher2000** · 2006-09-11 18:02

Do you get different results if Word is started without a document (i.e.g, just Start>Programs>MS Office>Word) and if Word is started by launching a document (either from Windows Explorer / desktop / email)? If so, it could be something in your code, but usually there is a different error message.

Otherwise, it probably isn't your macro that is the problem, but some other reference that has become invalid. Probably the systematic approach is best at this point.

**curious** · 2006-09-11 20:18

Thank you for your reply.

Since I don't know which macro will cause the message to appear, I can't determine if opening Word without a document would change the scenario. Strange that not all macros cause the message....

The next time I can't runa macro, I will close the document window, launched Word w/o a document, and see if I can then run the macro -- and will report back.

Thanks again for your attention to this.

Curious

Thread: Macro Security Setting (2002/SR2)

Thread Tools