Compile Error Automation Error Excel 2007
Contents |
SQL Server 2014 Express resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums excel vba compile error automation error Blogs Channel 9 Documentation APIs and reference Dev centers Retired content
Compile Error In Hidden Module Excel 2007
Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second.
Compile Error In Hidden Module Excel 2007 Macro
Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Excel VBA -- Compile Error:Automation Error Microsoft
Compile Error In Hidden Module Excel 2007 Windows 7
ISV Community Center > Visual Basic for Applications (VBA) Question 0 Sign in to vote I wrote an Excel VBA program for my company that has been utilized for about a year with over 350 users, all running Windows XP and Office 2007. A handful of users who receive a new laptop (same as mine), have compile error in hidden module thisworkbook excel 2007 experienced a "Compile Error: Automation Error" when they attempt to run the program. There are no error codes, and the compile error points to a procedure declaration that compiles fine on other PCs: "Public Function KeyFound(strKey As String, SourceCollection As Collection) As Boolean". I have commented out the procude only to get another compile error at a different procedure. I checked for missing references and found none; I have disabled any Add-Ins; I tried to delete all .EXD files; nothing works. One user reinstalled Office and got the program to run, another, needed to have IT rebuild his laptop and got it to work. I need to find the problem so I don't have to keep having users rebuild their laptops. Any help would be greatly appreciated. Thursday, April 26, 2012 3:23 PM Reply | Quote All replies 0 Sign in to vote I think the key is in the rebuild. The original build may not be a full installation and the rebuild is, or som
Buffington [MSFT]August 15, 201229 0 0 0 This article applies toWord, Access, Excel and PowerPoint. MS12-060 is a security update that was released Tuesday, August 14, 2012. This update replaced MS12-027. You may now be seeing compile error in hidden module sheet1 excel 2007 one of the following errors: "Unspecified Automation Error" when running or compiling your compile error excel 2010 Microsoft Office VBA code after installing MS12-060; or "Errors were detected while saving ‘filename.xlsm'. Microsoft Office Excel may be able automation error vba excel to save the file by removing or repairing some features. To make the repairs in a new file, click Continue. To cancel saving the file, click Cancel." clicking continue you will see "Document https://social.msdn.microsoft.com/Forums/en-US/72a8a9ce-6a4f-4137-8185-a351a2375e52/excel-vba-compile-errorautomation-error?forum=isvvba failed to save" or similar error. Update - 9/26/2012. See this blog post for the latest update. Fixit Available There is a fixit available for this problem: Office 2010 w SP1 - http://support.microsoft.com/kb/2597986 Office 2007 w SP2 or SP3 - http://support.microsoft.com/kb/2687441 Office 2003 w SP3 or Office 2003 Web Components w SP3 - http://support.microsoft.com/kb/2687323 Steps to fix the problem manually Alternatively, https://blogs.technet.microsoft.com/the_microsoft_excel_support_team_blog/2012/08/15/unspecified-automation-error-after-applying-ms12-060-updated-926/ the manual fix for this problem is to re-register MSCOMCTL.OCX. To do this, follow these steps: 1. Open an administrative-level command prompt. The command prompt MUST be on the administrative level for this to work. Click START, and type RUN in the run command line. On Windows Vista and Windows 7 you will see CMD.EXE appear in the quick searchlist. Right click CMD.EXE and left click Run As Administrator. A black command prompt opens. On Windows XP, there is no built-in run-as-admin, but you can use the run as menu option (or runas command line) to execute an admin command from a Limited User Account. 2. If on a 64-bit machine, type the following: regsvr32.exe /u C:\Windows\SysWOW64\MSCOMCTL.OCX Hit ENTER then type regsvr32.exe C:\Windows\SysWOW64\MSCOMCTL.OCX If on a 32-bit machine, type the following: regsvr32.exe /u C:\Windows\System32\MSCOMCTL.OCX hit ENTER then type regsvr32.exe C:\Windows\System32\MSCOMCTL.OCX Your Office program should work again after doing this. (Updated) 3. NOTE: The following step is done at your own risk. Microsoft doesn't know about any side effects to deleting this registry key. In cases where the re-registration doesn't work and you still get the error, you will need to open the registry editor (START > RUN > REGEDIT) and
here for a quick overview of the site Help Center Detailed answers to any questions http://stackoverflow.com/questions/34803843/excel-vba-automation-error-due-to-jan-2016-office-update-probably-caused-by-m you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community compile error of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Excel VBA “Automation Error” due to Jan 2016 Office Update, probably caused by MSCOMCTL.OCX (Microsoft Windows Common Controls 6.o (Service Pack 6)) up vote 8 down vote favorite 2 EDITED ONCE SOLUTION WAS FOUND: compile error in I have added a Treeview Active X Control to one of our spreadsheet, using Microsoft Windows Common Controls 6.0 (Service Pack 6), i.e. MSCOMCTL.OCX which lives in c:\Windows\SysWOW64\ KB2881029 (Security Update for Microsoft Office 2010 32-Bit Edition) (MS16-004), pushed out from Microsoft on the 15/01/2016 (or thereabout), installs a new MSCOMCTL.OCX (version 6.1.98.46 which was "Created" 9/12/2015, but "Accessed" (i.e. installed on the computer) at the time of the update). This made the workbook "loose" reference to MSCOMCTL.OCX (quote marks on "loose", because the reference is still ticked but no longer works, the workbook doesn't compile because of "Compile error: Object library feature not supported" or "Automation error") It seems that the update modifies the registry key HKEY_CLASSES_ROOT\TypeLib{831FDD16-0C5C-11D2-A9FC-000F8754DA1}\ by adding a SubKey 2.0, but leaves it empty, and doesn't register the new MSCOMCTL.OCX. Fixing the problem requires 3 steps: 1) MSCOMCTL.OCX. needs to be un-registered and re-registered (Start button/search/command/right click command prompt/run as admistirator: c:\Windows\system32>Regsvr32 /u C:\Windows\SysWOW64\MSCOMCTL.OCX c:\Windows\system32>Regsvr32 C:\Window