From: STeve Andre' (andres_at_msu.edu)
Date: Mon Aug 19 2002 - 22:25:10 EDT
I haven't seen this yet. Boy I hope my users won't see this... Hmmm.
I might try reinstalling Office 2000 to see what that does.
Sadly, this is the kind of problem where MS won't do much but tell you
to reinstall things. The trick is, whats the minimum that needs to be
reinstalled.
I'd try that first.
--STeve Andre'
On Monday 19 August 2002 07:56 pm, Stuart F. Biggar wrote:
> For those of you with Win2000 and SP3 on Thinkpads who might
> use Office 2000, I have a question. I'm using an A21p, 2629HTU
> with Win2000 as shipped by IBM, SP2 added by me, then recently
> SP3.
>
> Since installing SP3 on a working and up-to-date SP2 + recommended
> + critical updates from MS, whenever I start and exit an Office 2000
> application such as word or excel, I get an error box with a title
> of "Microsoft Visual Basic" with a single line of preceded by an
> ! in a yellow triangle:
>
> "Compile error in hidden module: AutoExec"
>
> with two boxes "OK" and "Help".
>
> Help says something about a module being protected and
> to unprotect it. I haven't a clue as to what module/file
> AutoExec is or where it might be. Searching for AutoExec*.*
> shows 5 files (Autoexec.nt_, several autoexec.bat files in
> the partition magic directory, autoexec.nt in \winnt\repair
> and autoexec.nt in c:\winnt\system32. Properties seem to
> allow changes by most any user ...
>
> If I select OK, the app starts (or exits) and seems to
> work OK. However, it is a nuisance.
>
> Sure would be nice to put the full path/filename into the
> error rather than just AutoExec - got to love MS.
>
> Any ideas on how to "fix" this new feature other than
> backing out SP3 or reinstalling or ????
>
> Thanks,
>
> Stuart
This archive was generated by hypermail 2.1.3 : Thu Jan 23 2003 - 09:59:14 EST