[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3069
  • Last Modified:

Microsoft Visual Basic Compile Error in hidden module: AutoExec

I have Office 2003 installed on my Windows XP machine.
Every time I open an Office App.  I get a Microsoft Visual Basic Error Box, 'Compile Error in hidden module: AutoExec'
I looked at documentation on this site but nothing worked.
0
sccomputers
Asked:
sccomputers
  • 2
  • 2
  • 2
1 Solution
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Is this an Access application, or does this occur in all Office products (Word, Excel, etc.)

If Access, hit {f11} to go to your Database Windows, then Tools menu: Options, View tab, check the Hidden Objects checkbox, and hit ok.
Then click on the Macros tab, and you should see a semi-greyed-out AutoExec macro.
Open it in design view, and tell us what it says.
0
 
byundtCommented:
Adobe Acrobat is a frequent cause of this problem. Office 2003 is not compatible with Acrobat 6 and earlier, yet Acrobat insists on installing its pdfmaker add-in in the start-up folders of Word and Excel. The Compile Error in hidden module: AutoExec is the result. Norton Anti-Virus is also a common cause of this error message. http://support.microsoft.com/kb/307410/en-us

0
 
sccomputersAuthor Commented:
I removed the pdfmaker.dot file from Office /  Startup folder.
I found the one for Excel in the  C:\Documents and Settings\User Name\Application Data\Microsoft\Excel\Xlstart and removed it but I still get the error, only in Excel though.  All other Office Apps. open without an error now.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
sccomputersAuthor Commented:
I ended up just removing Adobe Standard 6.0 and that went away.
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Learn something new every day.

Once I found out that a certain version of Macromedia DreamWeaver laid claim to the .asp extension, which cause all of our Web pages to open in DreamWeaver.  (or was it Adobe?)
0
 
byundtCommented:
I used Acrobat 5 instead of 6, but it installed an add-in in my C:\Program Files\Microsoft Office\Office11\XLSTART folder (for Excel) and in C:\Program Files\Microsoft Office\Office11\STARTUP (for Word). Both of these files needed to be removed to enjoy error-free use of Excel and Word.

To produce a .pdf file, my process was to do a "print to file" using a PostScript printer (such as the Apple LaserWriter, which I never owned but found that Windows would install the driver if asked nicely). I could then use Acrobat Distiller to convert that print file into a .pdf document.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now