↧
GARCH estimation returns 'NA'
↧
Misleading calculations of Endogeneous variables in system
Dear Gareth,
Thanks again. I have looked at it again. With your little exercise EViews worked well and as expected in my (old) workfile. So, I tied my own work in a newly created model in that workfile (rather than copying an existing one) and the error did not occur anymore.
Everything is fine now. I tried hard to find a setting in my old models different to the newly created ones but could not find any. Over time, the models must have become flawed.
Best regards
Chrisian
Thanks again. I have looked at it again. With your little exercise EViews worked well and as expected in my (old) workfile. So, I tied my own work in a newly created model in that workfile (rather than copying an existing one) and the error did not occur anymore.
Everything is fine now. I tried hard to find a setting in my old models different to the newly created ones but could not find any. Over time, the models must have become flawed.
Best regards
Chrisian
↧
↧
syntax cloroing
↧
object names
How hard would it be to get EViews to maintain the capitalization of names in displays. So that
series piValue = 3.14
would be displayed as "piValue" rather than either "pivalue" or "PIVALUE"?
I'm not suggesting changing the case-free notation. All three of the above would refer to the same variable. It would just make many long names easier to read.
Could this be done by having display names automatically generated consistent with the case written in the command and then changing the workfile page (by option) to show the display name?
series piValue = 3.14
would be displayed as "piValue" rather than either "pivalue" or "PIVALUE"?
I'm not suggesting changing the case-free notation. All three of the above would refer to the same variable. It would just make many long names easier to read.
Could this be done by having display names automatically generated consistent with the case written in the command and then changing the workfile page (by option) to show the display name?
↧
switchreg
↧
↧
switchreg
↧
Prg font colors are now missing?
I downloaded the latest update of EViews 9.5.
This resulted in that the font in my prg-files now is black. Before the update, all for-loops were blue, the apostrophe (which skips a line) resulted in a green font for this line, the normal code was black etc. Now, everything is black again. I want it to be as before again, or at least that there should be an option for choosing to have colors. Easier for follow the structure in the prg-file. So please change this - or tell me how to add this feature in the newest version of EViews.
This resulted in that the font in my prg-files now is black. Before the update, all for-loops were blue, the apostrophe (which skips a line) resulted in a green font for this line, the normal code was black etc. Now, everything is black again. I want it to be as before again, or at least that there should be an option for choosing to have colors. Easier for follow the structure in the prg-file. So please change this - or tell me how to add this feature in the newest version of EViews.
↧
Prg font colors are now missing?
↧
Merging 2 workpages
Hello,
I have a workfile with 2 pages and I'd like to merge them into one. Some series in the 2nd page don't exist in the 1st one and I'd like them to be integrated using 3 criteria (here: model, category and country).
![Image]()
I try to use the following command but it does not work:
copy(m) 2000PRSTEVFLEETBYAGE\* 19601999FLEETBYAGE\
Thank you for your help.
I have a workfile with 2 pages and I'd like to merge them into one. Some series in the 2nd page don't exist in the 1st one and I'd like them to be integrated using 3 criteria (here: model, category and country).

I try to use the following command but it does not work:
copy(m) 2000PRSTEVFLEETBYAGE\* 19601999FLEETBYAGE\
Thank you for your help.
↧
↧
Merging 2 workpages
↧
Prg font colors are now missing?
I guess you are interested in tips possible bugs, after installing the new patch for 9.5.
It seems as if the "capture" window for capturing the syntax cannot be "cleared". I have tried both using right click "select all" and "Clear", or my own keyboard. It cannot be cleared on my computer. That worked before the patch on my computer.
It seems as if the "capture" window for capturing the syntax cannot be "cleared". I have tried both using right click "select all" and "Clear", or my own keyboard. It cannot be cleared on my computer. That worked before the patch on my computer.
↧
Merging 2 workpages
↧
Merging 2 workpages
↧
↧
Opening text files from Google Drive
↧
normalize a group of variables
↧
ARDL bounds test incorrect critical values?
I have noticed when performing an ARDL bounds testing (k=11) with an unrestricted trend that the upper I(1) bound for the Pesaran bounds test appears to be incorrect (see image). My understanding is that they should be increasing and all looks fine until that one bound.
Is this incorrect, and does anybody know where I can find critical values for k=11 as the original paper only goes to k=10.
(I realise that k=11 is high but this is due to the number of official government office housing regions in the UK).
Thanks for your help
Is this incorrect, and does anybody know where I can find critical values for k=11 as the original paper only goes to k=10.
(I realise that k=11 is high but this is due to the number of official government office housing regions in the UK).
Thanks for your help
↧
ARDL bounds test incorrect critical values?
↧
↧
normalize a group of variables
↧
Opening text files from Google Drive
That is correct. Google drive permits files with the same name. 'Deleting'' doesnt actually delete it. It tags the file as hidden. EViews however cannot differentiate between hidden and non-hidden files
EViews has issues with files of the same name. We are working on that as well but it wont be in the next patch.
EViews has issues with files of the same name. We are working on that as well but it wont be in the next patch.
↧
Silent Installation and Silent Registration
To be up-front, we have a 25-seat lab license. It is not concurrent or unlimited, but unlike a standalone license, it is a shared serial number for all machines. The initial post here reads to me that remembering the license number in the install script would be all that is needed, but that does not silently register them. Instead, EViews opens to the register dialog window. I am assuming the user doing the registration must be an admin, but regardless, I can't trust students to deal with that!
When I use the /registerlicense switch, it also does not register. EViews opens to the register dialog window just as if I hadn't used any switch. The "Autoregister..." button shows the information provided when recording the installation script, and does not change based on anything I provide with the /registerlicense switch. (The "invalid switch" error mentioned in another response is because the EViews GUI is trying to interpret the switch text. Using single quotes, ', instead of double quotes, ", generates a different error.)
So, I can silently deploy the software, but not silently register it. What good is that? If any kind of license should allow for silent install AND registration, it should be a lab/classroom where all the installs are automated and nobody is an admin!
Any advice?
When I use the /registerlicense switch, it also does not register. EViews opens to the register dialog window just as if I hadn't used any switch. The "Autoregister..." button shows the information provided when recording the installation script, and does not change based on anything I provide with the /registerlicense switch. (The "invalid switch" error mentioned in another response is because the EViews GUI is trying to interpret the switch text. Using single quotes, ', instead of double quotes, ", generates a different error.)
So, I can silently deploy the software, but not silently register it. What good is that? If any kind of license should allow for silent install AND registration, it should be a lab/classroom where all the installs are automated and nobody is an admin!
Any advice?
↧