EViews.com

There appears to be an issue with the way the EViews 13 COM Automation interface is handling the include statement. I've attached a short sample program to demonstrate the issue. Please unzip the contents to C:\temp and run the eviewscom.exe program.

When the EViews 12 version of EViewsMgr.dll is registered, the program behaves as expected.

However, when the EViews 13 version of EViewsMgr.dll is registered, the program crashes at (or just after) the include statement. I believe that the root cause is that the program variable %afile is going out of scope across the include statement and generating an access violation. It's almost as if it's treating the include as an exec statement instead - for which the program variables would be expected to go out of scope.

Note that if you run the eviewsmgr.prg directly in the EViews 12 or 13 environment, it behaves as expected and creates a series x with the constant value of 1 in the workfile work.wf1.

Thanks for the bug report.

This was an issue that was caused by incorrect handling of an include when a program is called via EXEC. I don't think this would've happened if you had used the RUN command instead. This will be fixed in the next patch.

FYI, you should use the following relative path when you perform the include statement (line 4 below): This way, the include will try to look for the program file in the same directory as the parent program. Without this, my attempts to run your program initially failed since my default directory was not c:\temp (but the files I was running were as you directed).

Steve

Thanks Steve! Looking forward to the next patch. Do you have any idea when that will be released?

Within a day or two