Compile error in hidden module

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

R.S.Lynn - 01 Dec 2006 17:57 GMT

The Visual Basic error window that popped up is
"Compile error in hidden module: <module name>
A protected module can't be displayed. This error has the following cause
and solution:

a.. There is a compilation error in the code of the specified module, but
it can't be displayed because the project is protected.
Unprotect the project, and then run the code again to view the error."

I do not know how to "select the item in question." I do not know how to
"unprotect
the project and then run the code again to view the error."

I suspect that something has been corrupted in my Office 2003. Do I have
any alternative to reinstalling the whole Office? Please know that I get
similar messages now in Word.

If I simply select OK, the programs seem to proceed without any error I can
see.
The modules have names like AutoExecNew and DistMon.

Reply to this Message

Gord Dibben - 01 Dec 2006 18:31 GMT

The <module name> would give us more to work on but this a common error caused
by PDFMaker.xla.

See KB article http://support.microsoft.com/default.aspx?scid=kb;EN-US;q307410

The PDFMaker.xla and maybe PDFMaker.dot are stored in your Office\XLSTART folder
or in the Excel\XLSTART folder.

Any files in these folders will open with Excel.

You must remove them from the XLSTART folder.

Gord Dibben MS Excel MVP

>The Visual Basic error window that popped up is
>"Compile error in hidden module: <module name>
[quoted text clipped - 16 lines]
>see.
> The modules have names like AutoExecNew and DistMon.

Gord Dibben MS Excel MVP

Reply to this Message

Dave Peterson - 01 Dec 2006 18:40 GMT

And you have similar replies to your other post.

> The Visual Basic error window that popped up is
> "Compile error in hidden module: <module name>
[quoted text clipped - 16 lines]
> see.
> The modules have names like AutoExecNew and DistMon.

Signature

Dave Peterson

Reply to this Message

Rate this thread: