EViews.com

Hi,
I was running my eviews workfiles through an excel macro on eviews 7. I upgraded to Eviews 8 briefly then 9 and now when I open a workfile (most of them actually), I get:

1) EViews7 - A crash ("EViews has stopped working") when opening the workfile on EViews7 followed by a restart of EViews
2) EViews8 - Attached error below. Says something about a partial load of an object failing
3) EViews9 - No error, the file opens but takes long to run

I suppose the solution would be to run the workfiles through Eviews9 instead of EViews 7 as originally but I don't think I can do that because EViews 9 takes too long to run the program/workfile. Any help explaining why I'm getting this error? Is the workfile incompatible between Eviews 7 and Eviews9?

Thank you very much in advance!

I think I found the problem. All my workfiles have equations estimated using eq1.ls(h)

When opened in Eviews 9, my guess they automatically change to ARMA ML? When saved and re-run using Eviews9, it is incompatible and hence crashes?

"With few exceptions, EViews 9 workfiles are backward compatible with EViews 8. Note that the following objects are new or have been modified in Version 9:
• Equation objects estimated with methods that employ new features (threshold regression, ARDL, ML ARMA, ARFIMA.)

If you have saved workfiles containing any of the above objects and open them in EViews 8 or earlier, EViews will delete the incompatible object and notify you that one or more objects were not read. If you then save the workfile, you will lose the objects. We recommend that you make a copy of any workfiles that contain these objects if you would like to use these workfiles in earlier versions of EViews"

Am I right on this? Any solution? Could you tell me what the EViews9 equivalent of eq1.ls(h) is? Thanks

From the Object Reference:

EViews 7 shouldn't crash. The partial load is the correct behavior. We'll take a look on the ev9 side.

Thanks guys. I managed to solve it the other way using the white paper on COM automation and inserting the line into my VBA that defaulted to eviews9 over eviews7. I also removed autosearch and now it's as fast as it used to be. Thanks once again!

Does that mean your VBA code is now explicitly using EViews 7 all the time? So the issue with EViews 9 hasn't been resolved?