I have developed a macro in VBA Excel 2016, which extracts information from emails in Outlook (sender, subject, date, etc), and exports this information in an Excel sheet.
The code works fine in Excel 2016, however, in Office 2013 versions I get the following error:
Automation error. Object library not registered
I would greatly appreciate if someone could help me solve this error.
This error appears in the following line of the code:
Set olNs = olApp.GetNamespace ("MAPI")
Actually, I already solved the issue. It was so simply as, when defining the correct libraries for 2013 office, saving the file, closing it, and then opening it again and then running the macro.
But anyway, thanks guys!
Related
I have a problem with opening an old excel file with VBA macros. It looks like some of the VBa libraries are no longer used in excel 365.
While opening I get an error:
Opening the VBA project in this file requires a component that is not currently installed. This file will be opened without the VBA project. Fro more information, search Office.com for "VBA converters"
I struggle to install those libraries on my PC, but in the meantime I wonder if there is any workaround to get the VBA code out of this file.
Thanks in advance!
EDIT:
I attached mentioned file.
https://docs.google.com/spreadsheets/d/1msKl4kZANwwOTcqkDDb6pUjaaYkZ57lS/edit?usp=sharing&ouid=105093812803215551016&rtpof=true&sd=true
You can solve your problem when install office2003 and save it to microsoft office excel workbook(*.xls)
Link for office 2003
Your file after convert
Thanks for Mr.Yasserkhalil
I am relatively new to VBA programming and I have come across a debug error for a macro we use at work. the macro was written by another colleague who has no left the company. I will explain what happens originally the macro ran on windows 7 Microsoft 0ffice 2010 with no faults no we have migrated to windows 10 Microsoft Excel office 365 I get "run time error '5'" invalid procedure when I debug it is failing at the below code
AppActivate "Microsoft Excel"
is it because excel is referenced differently in 365 any assistance would be greatly appreciated
thank you Chris
We recently had a new employee join our (very small) company, and he is using Excel 2010 while the rest of the office uses Excel 2016.
When he attempts to run a macro which draws a chart, he gets an error message that says:
Compile Error - Method or Data member not Found
However, this error message doesn't appear when I run the exact same macro in Excel 2016.
The line of code which appears to be throwing up a problem is the following:
ActiveChart.FullSeriesCollection(1).Format.Line.ForeColor.ObjectThemeColor = msoThemeColorText2
Has anyone come across this problem before? And is there any quick solution, besides the obvious of switching him to Excel 2016 like the rest of us?
Thanks in advance.
I'm encountering the following error whenever I tried to run my xlsm in excel 2010.
Complex formatting that is applied to the selected chart may take a
while to display. Do you want to continue using the formatting?"
But my xlsm works fine in excel 2013 and excel 2016.
Please anyone suggest solution to resolve this.
If you have access to the VBA code, try writing the following in the Private Sub Workbook_Open():
Do
DoEvents
Loop Until Application.Ready()
Source: From here.
I have a very old VB6 application, we have lost the source code. It can call excel 2003, 2007 to
Launch excel
Insert value to the new sheet cells.
I guess it use com to automate the excel, anyway we lost the source code and cannot contact the programmer.
After we upgrade the office to 2010, it cannot insert value anymore, just a blank sheet ....why?
Do anyone have the same experience as me? old win32 program work on excel 2003/2007 , but don't work on 2010.
Attach screenshot for your reference:
when using excel 2007 , it can fill the value to sheet.
when using excel 2010 , it cannot, and the windbg show some exceptions, how can I troubleshoot it?
Even if you could trace/capture, I don't think that would help you much.
Based on the simplicity of the code, you would be better off remaking it from scratch. If it's something proprietary and very useful, you should probably consider having both versions installed at the same time, which has worked for me just fine.