Issues when importing multiple sheets from Excel to Eviews 7
Posted: Tue Mar 22, 2016 5:31 am
First post and relatively new when it comes to Eviews, so be gentle.
I'm currently working on my masters thesis. For the thesis I have collected daily return data on 169 different Norwegian stocks and 3 indices, dating back to january 1990 for some stocks.
I thus have an excel file containing 172 sheets of data that I want to import into Eviews, with anywhere from around 2000 observations up to around 5000 observations for each stock.
Searching for a solution on how to import the sheets led me to this froum, and I found this code:
The issue is that only half of the sheets from the excel-file appears to be stored into EViews. However, the program seems to run through all 172 sheets.
So, is there a remedy for this? Is the code flawed or is the dataset too large in terms of # of observations?
I'm currently working on my masters thesis. For the thesis I have collected daily return data on 169 different Norwegian stocks and 3 indices, dating back to january 1990 for some stocks.
I thus have an excel file containing 172 sheets of data that I want to import into Eviews, with anywhere from around 2000 observations up to around 5000 observations for each stock.
Searching for a solution on how to import the sheets led me to this froum, and I found this code:
Code: Select all
%filename = "f:\OSEAXRet.xlsx" 'file name of the file to be opened
%sheetnames = @tablenames(%filename) 'find the names of the sheets in that file
%sheetname = @word(%sheetnames,1) 'get the first sheet name
wfopen(wf=panel,page=%sheetname) %filename range=%sheetname 'open the first sheet as a new workfile (with name=panel, and pagename=the first sheet name)
'loop through the remaining sheets, loading them into the workfile one at a time
for !i=2 to @wcount(%sheetnames)
%sheetname = @word(%sheetnames, !i) 'get the name of the next sheet
pageload(page=%sheetname) %filename range=%sheetname 'load the next sheet
nextSo, is there a remedy for this? Is the code flawed or is the dataset too large in terms of # of observations?