several bugs - opening files, updating, mods not running correctly
Posted: Wed Jun 19, 2024 9:01 am
I am having several basic functionality issues with Eviews.
First, I have a specific program that Eviews is repeatedly not able to open, either when I navigate to the program in File Explorer or when I try to mouse-click Open via Eviews. My other programs, including those in the same folder, are able to be opened. This is a new problem, as I have previously been able to open and edit the program normally.
This specific program is set as an addin. I am editing it to incorporate new lines. These lines work correctly when I click to Run the program (note that to do so I opened the program in Notepad, then pasted into a new Eviews program because I cannot open the program through Eviews). However, they do NOT seem to be included when I run the program as an addin command (either from the pulldown or by typing its command), nor do they work when I type "RUN filepath\program.prg". I deleted the original program, both as an addin and directly in File Explorer, and re-saved/re-addin-ed the edited program, so this should not be an issue of my changes not being saved correctly. The involved lines attempt to use the model.control command; I also tried a "hack" version of this command (genr series_a=series_a+(series_target-series)), which had the same problem of seemingly not being included because the target/add factor did not get modified, so I do not think this is a specific issue with the command. This is a workhorse program that I use to solve and iterate a model dozens of times in a working session, so it is a major efficiency drag to have to access and run the program in such a roundabout way, and I need to be able to rely on changes to programs being incorporated.
My Eviews is 13, April 24th build, Enterprise. I attempted to update, but have been getting told to close all instances of Eviews even though all instances are already closed. I restarted my computer and am still receiving these messages. [Sorry, in my title I said "mods". My personal naming convention for most addins is to call them "mods", so I often slip into calling them that.]
First, I have a specific program that Eviews is repeatedly not able to open, either when I navigate to the program in File Explorer or when I try to mouse-click Open via Eviews. My other programs, including those in the same folder, are able to be opened. This is a new problem, as I have previously been able to open and edit the program normally.
This specific program is set as an addin. I am editing it to incorporate new lines. These lines work correctly when I click to Run the program (note that to do so I opened the program in Notepad, then pasted into a new Eviews program because I cannot open the program through Eviews). However, they do NOT seem to be included when I run the program as an addin command (either from the pulldown or by typing its command), nor do they work when I type "RUN filepath\program.prg". I deleted the original program, both as an addin and directly in File Explorer, and re-saved/re-addin-ed the edited program, so this should not be an issue of my changes not being saved correctly. The involved lines attempt to use the model.control command; I also tried a "hack" version of this command (genr series_a=series_a+(series_target-series)), which had the same problem of seemingly not being included because the target/add factor did not get modified, so I do not think this is a specific issue with the command. This is a workhorse program that I use to solve and iterate a model dozens of times in a working session, so it is a major efficiency drag to have to access and run the program in such a roundabout way, and I need to be able to rely on changes to programs being incorporated.
My Eviews is 13, April 24th build, Enterprise. I attempted to update, but have been getting told to close all instances of Eviews even though all instances are already closed. I restarted my computer and am still receiving these messages. [Sorry, in my title I said "mods". My personal naming convention for most addins is to call them "mods", so I often slip into calling them that.]