Excel 2007 Autoexecnew Compile Error
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 13 Oct 2016 21:24:30 GMT by s_ac4 (squid/3.5.20)
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full
Compile Error In Hidden Module Link Mac
Time Job Ways to Get Help Expand Search Submit Close Search Login Join compile error in hidden module mac Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Compile Error word compile error in hidden module link in Hidden Module: Excel 2007 Want to Advertise Here? Solved Compile Error in Hidden Module: Excel 2007 Posted on 2007-05-22 Adobe Acrobat MS Excel 1 Verified Solution 6 Comments 13,637 Views Last Modified: http://answers.microsoft.com/en-us/msoffice/forum/msoffice_excel-mso_other/compile-error-in-hidden-module-distmon/35685af1-79a0-4907-87da-fd5fac8c3b50 2010-08-24 I'm receiving an error when Excel 2007 opens 'Compile Error in Hidden Module: AutoExecNew' and an error when Excel 2007 closes 'Compile Error in Hidden Module: DistMon' Microsoft knowledge base says to look for two Adobe files Pdfmaker.dot Pdfmaker.xla and delete them out of the startup folder; however, I don't see them in the folder. Any suggestons? 0 Question by:sgreene63 Facebook Twitter LinkedIn Google LVL 85 https://www.experts-exchange.com/questions/22587269/Compile-Error-in-Hidden-Module-Excel-2007.html Best Solution byRory Archibald There are two XLSTART folders. One in the MS Office installation directory - something like C:\Program Files\Microsoft Office\Office12 - and the other in your C:\Documents and Settings\*username*\Application Go to Solution 6 Comments LVL 85 Overall: Level 85 MS Excel 85 Adobe Acrobat 1 Message Accepted Solution by:Rory Archibald2007-05-22 There are two XLSTART folders. One in the MS Office installation directory - something like C:\Program Files\Microsoft Office\Office12 - and the other in your C:\Documents and Settings\*username*\Application Data\Microsoft\Excel directory. The latter is usually a hidden directory so you may need to go into Windows Explorer, and select Tools-Folder Options and on the View tab, click the Show hidden files and folders option. You can also locate the xla via a search as long as you select the option to include hidden files and folders. HTH Rory 0 LVL 17 Overall: Level 17 MS Excel 17 Message Expert Comment by:LoNeRaVeR92007-05-22 sgreene63: Did you check the Windows startup folder or the Excel startup folder? The Excel startup folder should be found at the following path. C:\Program Files\Microsoft Office\OFFICE12\XLSTART Kindest Regards, Jaes 0 LVL 10 Overall: Level 10 MS Excel 4 Message Expert Comment
get the following error when you start Excel 2003 or Excel 2007: "Compile Error in Hidden Module: Distmon" Cause: The cause of this error is PDFMaker.xla, which loads at startup. Solution: The easiest solution is to delete PDFMaker.xla http://www.itexperience.net/2008/08/21/compile-error-in-hidden-module-distmon-in-excel-2003-and-2007/ from your computer. Since Adobe Professional 8 uses DLL-addins to add the toolbar in Excel, https://www.youtube.com/watch?v=taeQkJ5THvQ you can safely delete the PDFMaker.xla file on your computer. PDFMaker.xla may be at one or more locations on your computers. Typically, PDFMaker.xla is stored in your profile directory: C:\Documents and Settings\
Du siehst YouTube auf Deutsch. Du kannst diese Einstellung unten ändern. Learn more You're viewing YouTube in German. You can change this preference below. Schließen Ja, ich möchte sie behalten Rückgängig machen Schließen Dieses Video ist nicht verfügbar. WiedergabelisteWarteschlangeWiedergabelisteWarteschlange Alle entfernenBeenden Wird geladen... Wiedergabeliste Warteschlange __count__/__total__ 8 (SOLVED )Compile Error in Hidden Module Module 1/ 2/ 3 (Tax Query by Harmeet) Make Knowledge Free AbonnierenAbonniertAbo beenden39.83139 Tsd. Wird geladen... Wird geladen... Wird verarbeitet... Hinzufügen Möchtest du dieses Video später noch einmal ansehen? Wenn du bei YouTube angemeldet bist, kannst du dieses Video zu einer Playlist hinzufügen. Anmelden Teilen Mehr Melden Möchtest du dieses Video melden? Melde dich an, um unangemessene Inhalte zu melden. Anmelden Transkript Statistik 60.588 Aufrufe 22 Dieses Video gefällt dir? Melde dich bei YouTube an, damit dein Feedback gezählt wird. Anmelden 23 3 Dieses Video gefällt dir nicht? Melde dich bei YouTube an, damit dein Feedback gezählt wird. Anmelden 4 Wird geladen... Wird geladen... Transkript Das interaktive Transkript konnte nicht geladen werden. Wird geladen... Wird geladen... Die Bewertungsfunktion ist nach Ausleihen des Videos verfügbar. Diese Funktion ist zurzeit nicht verfügbar. Bitte versuche es später erneut. Veröffentlicht am 31.07.2013Using Windows XP service pack 2 and getting this bug when trying to generate XML using ITR workbook I must admit that this was a strange bug for i personally didn't face it since i have a service pack 3 for windows XP but few people using service pack 3 also complain of this bug .One of my subscriber's while trying to fill the return (excel workbook ITR 1 )was getting this message .After analysing the message he got via his send email screenshot and going through his comments , i understood that it was not easy for me to replicate the problem because it seemed to be a operating system issue and in my parent laptop ,it didn't seem a good idea to virtualise (create a seperate system for this version of windows XP),so i virtualised my other laptop and yes the bug did came in service pack 2 , .Basically the VB coding done vide modules used to generate the Extended mark up document don't compile properly with versions of windows XP OS lesser than service pack 3 version...so people using windows XP service pack 2 might face this problem ,because when i installed windows XP service pack 2 in one of my 5 laptops , i got the same error ,Firstly pressing alt +F11 opens up the visual basic editor which shows the module whic