Could some one tell me how it is possible to read aremos files in eviews using the programming command. In previous versions there was specific commans as tsdload or tsdftech but think that there are out of date in the latest version because nothing appears on thses commands on the programming reference book.
It is than possible to write Wfopen(type=a) …. ou wfopen(type=tsd)…but is tehre any other options available.
please let me know if you have an answer as soon as possible
reading aremos tsd files
Moderators: EViews Gareth, EViews Steve, EViews Moderator, EViews Jason
-
EViews Gareth
- Fe ddaethom, fe welon, fe amcangyfrifon
- Posts: 13603
- Joined: Tue Sep 16, 2008 5:38 pm
Re: reading aremos tsd files
DBOPEN is the command you want.
Re: reading aremos tsd files
I'm having some trouble here. Dbopen works fine when the tsd file is in some places but not in others.
dbopen(type=tsd) c:\temp\aremos\csvexp.tsd
yields an empty workfile, while
dbopen(type=tsd) K:\temp\aremos\csvexp.tsd
gives me the series that I want. The same goes for opening the files via File/Open/Database and choosing "Aremos TSD File". However, File/Open/Foreign Data as Workfile... works like a charm no matter where I place the tsd file. Is there a programming equivalent to "File/Open/Foreign Data as Workfile..."?
//F
dbopen(type=tsd) c:\temp\aremos\csvexp.tsd
yields an empty workfile, while
dbopen(type=tsd) K:\temp\aremos\csvexp.tsd
gives me the series that I want. The same goes for opening the files via File/Open/Database and choosing "Aremos TSD File". However, File/Open/Foreign Data as Workfile... works like a charm no matter where I place the tsd file. Is there a programming equivalent to "File/Open/Foreign Data as Workfile..."?
//F
-
EViews Chris
- EViews Developer
- Posts: 161
- Joined: Wed Sep 17, 2008 10:39 am
Re: reading aremos tsd files
I think the command you're looking for is
wfopen c:\temp\aremos\csvexp.tsd
If you just do 'open' (or 'dbopen') EViews will treat the tsd file as a database. 'wfopen' tells EViews to try to create a workfile from the TSD file (which is the same as 'Open Foreign Data As Workfile').
We normally treat TSD files as databases because they can contain a mix of frequencies (while an EViews workfile must have all series at a single frequency). When you use 'wfopen' on the TSD file it will force a frequency conversion of all series in the TSD file to the same frequency (if they aren't already), so it is potentially more 'destructive'.
Not sure why you're seeing problems with the different directories with dbopen. I haven't heard of a problem like that before. Are you sure that the files in the two locations contain exactly the same data? (A TSD file is actually just a text file, so you can open it for viewing with something like Windows Notepad).
wfopen c:\temp\aremos\csvexp.tsd
If you just do 'open' (or 'dbopen') EViews will treat the tsd file as a database. 'wfopen' tells EViews to try to create a workfile from the TSD file (which is the same as 'Open Foreign Data As Workfile').
We normally treat TSD files as databases because they can contain a mix of frequencies (while an EViews workfile must have all series at a single frequency). When you use 'wfopen' on the TSD file it will force a frequency conversion of all series in the TSD file to the same frequency (if they aren't already), so it is potentially more 'destructive'.
Not sure why you're seeing problems with the different directories with dbopen. I haven't heard of a problem like that before. Are you sure that the files in the two locations contain exactly the same data? (A TSD file is actually just a text file, so you can open it for viewing with something like Windows Notepad).
Who is online
Users browsing this forum: No registered users and 2 guests
