Hi, I use EViews 7.2 (Jan. 2. 2013) and Excel Professional plus 2010. I am controlling EViews by VBA.
The following code has some limitations depending on the size of the sample:
Public Vnames As Variant
Vnames = App.Get("@datestr(@date,""YYYY[q]Q[ ]"")")
Up to a sample size of 200-300 elements (the number is different for different samples) it’s OK, but in case of higher size Excel reports an error. There is no error notification in the com.log of EViews. Where are the limits? Could you expand these?
Thanks
The first answer comes from me.
At home I don’t have any problem with that issue at all.
I have a single license run at home – in institute EViews is on a server.
At home I have the update from Apr. 16. 2013.
At home I am sure that all installations/updates have been run without error to the default sites. Also all registering of add-ins have been successful executed, no further claims do appear at starting of EViews.
At home I have Excel Enterprice 2007.
The first check I can do in the institute to let EViews update on the April 2013 version.
The good news on the new day: As the Apr. 16. 2013 update was installed in the institute, my program is running also at work.
Application.get limitations
Moderators: EViews Gareth, EViews Moderator, EViews Jason, EViews Matt
-
EViews Steve
- EViews Developer
- Posts: 844
- Joined: Tue Sep 16, 2008 3:00 pm
- Location: Irvine, CA
Re: Application.get limitations
Ok, first of all, what error is reported by EViews? Is it an out of memory problem? Or something else?
Second, if Excel 2007 works but Excel 2010 does not, wouldn't that be an Excel issue? We just publish a generic COM interface. There isn't anything in the interface that is specific to Excel (except for NA handling). I can tell you that inside EViews, we don't put in any artificial limits on how many elements can be returned by a single Get call. You're only limited by memory.
If updating EViews made it work, I would suspect that you're running into a memory issue. When EViews starts up, it reserves a large amount of memory address space in order to load potentially very large workfiles. This can cause problems for other programs (such as Excel) that might need a lot of memory itself, or even Windows in order to allow a large amount of data to pass from COM. You can increase the amount of memory that EViews leaves for other processes by going to the EViews->Options Menu->Advanced system options and selecting a larger number in the dropdown next to "Memory reserved for Windows, DLL files, etc.", then restart EViews.
Steve
Second, if Excel 2007 works but Excel 2010 does not, wouldn't that be an Excel issue? We just publish a generic COM interface. There isn't anything in the interface that is specific to Excel (except for NA handling). I can tell you that inside EViews, we don't put in any artificial limits on how many elements can be returned by a single Get call. You're only limited by memory.
If updating EViews made it work, I would suspect that you're running into a memory issue. When EViews starts up, it reserves a large amount of memory address space in order to load potentially very large workfiles. This can cause problems for other programs (such as Excel) that might need a lot of memory itself, or even Windows in order to allow a large amount of data to pass from COM. You can increase the amount of memory that EViews leaves for other processes by going to the EViews->Options Menu->Advanced system options and selecting a larger number in the dropdown next to "Memory reserved for Windows, DLL files, etc.", then restart EViews.
Steve
Who is online
Users browsing this forum: No registered users and 2 guests
