Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Compile error in hidden module: AutoExecNew 1

Status
Not open for further replies.

harrymossman

Technical User
Sep 5, 2002
255
US
I have looked at 3 threads related to "Compile error in hidden module: AutoExecNew" but none seems to fix my problem.

I am running Windows XP professional 2002. I recently un-installed Acrobat professional. Now I get the error.

The advice in Thread 68-951767 (below) looked right on, so I tried it. But AcrobatPDFMaker was not checked, nor anything else related to Acrobat.

Hary

>>In the VB Editor, Tools/References -- and look for a CHECKED reference to AcrobatPDFMAker. UNCHECK it.

 
Hi Harry,

Acrobat is almost certainly the culprit. You don't say which app you are having trouble with. Look in all the places where things which open automatically might be stored and delete anything to do with acrobat.

For Word:

Documents and Settings\userid\Application Data\Microsoft\Word\STARTUP

(or whatever is specified under Tools > Options > File Locations tab > Startup), and also

(Office Installation root e.g. Program Files\Microsoft Office)\Office\Startup

(or ...Office10\Startup or ...OFFICE11\Startup depending on version)

For Excel try similar locations but substitute Excel for Word, and XLStart for Startup

Enjoy,
Tony

--------------------------------------------------------------------------------------------
We want to help you; help us to do it by reading this: Before you ask a question.
Excel VBA Training and more Help at VBAExpress[
 
Thanks for the tip! (The program is Excel.)

I went to C:\Documents and Settings\mossmanh\Application Data\Microsoft\Excel\XLSTART and deleted PDFMaker.xla. That did the trick.
 
The number of threads that have Adobe Acrobat as the culprit is amazing. Is this a Microsoft problem or an Adobe problem?

Gerry
 
OK, I REALLY need to figure this out! I have this problem with an installation of Office2000 on a machine that DOESN'T EVEN HAVE ACROBAT INSTALLED!!

I installed WinXP Pro, SP2, then Office, then Windows and Office updates from MS. That's all that's been done.

Now, I have seen this error before too, and the ONLY thing that resolved it was to reinstall the Acrobat Standard that had been installed previously. Not just Reader, either, that didn't cut the mustard. I had to install the full monty to get the error to go away.

So, I aks ya, what causes this *&^% and how the #@$% am I supposed to get rid of this error??!! Has ANYBODY seen a different approach to this?
 
Hi bankboysb,

There are other programs which can cause this - it's just that Acrobat is the most common.

It is (almost certainly) caused by a file which opens automatically at application startup (you don't say which app(s) are giving problems - check the locations in my fisrt post and delete things one by one until you find the culprit. You might also try removing any AddIns you have installed.

If you still have a problem when all templates and addins are gone, try deleting normal.dot (if it's Word) and if that fails I know nothing short of a virus which can cause it. Do you really have this on a completely clean new installation?

Enjoy,
Tony

--------------------------------------------------------------------------------------------
We want to help you; help us to do it by reading this: Before you ask a question.
Excel VBA Training and more Help at VBAExpress[
 
I have found in the past that it matters whether Acrobat is installed on top of Office, or vice versa.
 
Well, this may sound absurd, but despite the fact this was a perfectly clean install of WinXP and Office2K I came back to this machine this morning and discovered an installation of Acrobat5! Don't know where it came from! Honest to goodness I cannot figure out where it came from.

SO, at that point I looked into the pdfmaker files, found them and moved them. Having seen this problem before on machines where there were no startup files involved I am not surprised by how screwed up things can get with Office and XP.

So THANKS Y'ALL!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top