Hi
When using the fetch command ie. fetch(d="DS_DB",link,c=l) USE$EF.. with a ticker containing illegal characters, it appears that the link does not get created.
Thanks in advance for your help.
Using Eviews 9 May 27 2015 build
Best regards
Rasmus
Serial: 90C05629
link statement ignored if illegal characters
Moderators: EViews Gareth, EViews Moderator
Re: link statement ignored if illegal characters
I'm also having problems with links in Eviews 9. This code works in Eviews 8 (Annes grade is 2 in year 3) but in Eviews 9 I only get NA for all observations:
Code: Select all
WfCreate C:\temp\test u 4
Pagerename untitled p1
series year = @obsnum
alpha Name
Name(1) = "Jane"
Name(2) = "Bob"
Name(3) = "Anne"
Name(4) = "Pete"
Series grade = 2
PageCreate (page=p2) u 4
series year = @obsnum
link AnnesGrade
AnnesGrade.linkto(c=unique, smpl="if @upper(Name)=""Anne""") p1\Grade @src Year @dest Year
-
EViews Steve
- EViews Developer
- Posts: 844
- Joined: Tue Sep 16, 2008 3:00 pm
- Location: Irvine, CA
Re: link statement ignored if illegal characters
ErikG:
Your issue looks like a bug in 8, not 9. Your sample IF condition explicitly states:
which (if done correctly), will never be true as "Anne" is mixed case and @upper of anything will always be uppercase only.
You are correct in saying this works in 8 and I'm not sure why. In fact, in version 8, if I switch back to the first page of the workfile and type in:
into the command window, EViews 8 correctly states:
In any case, this "bug" has been fixed in 9 which is why you're seeing different behavior. You should change your if condition to be:
or
to perform the match correctly.
Rousing, I'll look at your issue next...
Steve
Your issue looks like a bug in 8, not 9. Your sample IF condition explicitly states:
Code: Select all
if @upper(name) = "Anne"You are correct in saying this works in 8 and I'm not sure why. In fact, in version 8, if I switch back to the first page of the workfile and type in:
Code: Select all
smpl if @upper(Name)="Anne"Code: Select all
Warning: Sample contains no observations.Code: Select all
smpl if @upper(Name)="ANNE"Code: Select all
smpl if @upper(Name)=@upper("Anne")Rousing, I'll look at your issue next...
Steve
Re: link statement ignored if illegal characters
Thanks, it could be that it is isolated to datastream fetches
-
EViews Steve
- EViews Developer
- Posts: 844
- Joined: Tue Sep 16, 2008 3:00 pm
- Location: Irvine, CA
Re: link statement ignored if illegal characters
Rasmus:
I tried importing a series object with the name "y1$test" from an EViews database, and it seemed to import ok and the link was created fine.
Which illegal character were you trying to import? And which database was the source? Can I get a copy of this database (if it's a file)?
Steve
I tried importing a series object with the name "y1$test" from an EViews database, and it seemed to import ok and the link was created fine.
Which illegal character were you trying to import? And which database was the source? Can I get a copy of this database (if it's a file)?
Steve
-
EViews Steve
- EViews Developer
- Posts: 844
- Joined: Tue Sep 16, 2008 3:00 pm
- Location: Irvine, CA
Re: link statement ignored if illegal characters
Rasmus:
I tried retrieving your "USE$EF.." object from DataStream and I get a linked series object whose name is: USE$EF__
and the link seems to exist. I can update just fine. I did this via both command window and via a program and the results were the same.
Are you doing anything different?
Steve
I tried retrieving your "USE$EF.." object from DataStream and I get a linked series object whose name is: USE$EF__
and the link seems to exist. I can update just fine. I did this via both command window and via a program and the results were the same.
Are you doing anything different?
Steve
Re: link statement ignored if illegal characters
It looks like the most recent patch has taken care of the problem :) - just tried with an old version Apr 3 2015 build (I have not updated so frequently at home - and here the issue remained) - after updating to the latest patch the problem is gone (so the issue must have been addressed after the Eviews 9 May 27 2015 build - which I was using at work at the time)
Anyways, thanks a lot for your help :)
Anyways, thanks a lot for your help :)
Who is online
Users browsing this forum: No registered users and 2 guests
