Opening Stata 13 in Stata 12 & WIOD Data

[Christos Makridis]

Hi all,

I am trying to use the World Input Output Database (http://www.wiod.org/new_site/database/seas.htm), which is in stata 13. While I've followed the direction to use "ssc install use13", I still cannot open the database.

I thought there might be another step that I'm overlooking, but I've read the instructions that they posted and don't see anything else.

Any ideas?

[Sergiy Radyakin]

...., I still cannot open the database.

What commands did you run?
What error messages did you get?

Best, Sergiy

[Christos Makridis]

Thanks for the reply Sergiy! I actually sent you an email last night with a screen shot of the error since I thought it would be more convenient for you than checking here.

I follow the two steps in the pdf you included, namely using ssc install use13 and opening the file -- just like any other file I routinely open -- with quotes. For example, I open:
use "C:\Publication and research\Journal Articles\2013 - Carbon taxes and Productivity\data\WIOD\wiot_full.dta"

It looks like it should be pretty simple, so I was surprised and just figured it was something basic I ignored..?

[Nick Cox]

It's not sufficient to install use13. It's not like downloading a software patch or fix. You need to use it explicitly instead of use when it's needed.

[Christos Makridis]

Perfect, thank you -- fixed!

[Sergiy Radyakin]

Nick Cox is absolutely correct. Built-in commands are not affected by the use13 program. This is described in the clarification on the built-in commands and applies to use, append, merge, etc commands that work with files. If you need to manipulate Stata 13 files in earlier Statas you first convert the file to your Stata's version with the help of use13, than do any manipulations with it with standard commands.

I actually sent you an email last night with a screen shot of the error since I thought it would be more convenient for you than checking here.

It's probably better to post it to Statalist. You get the answer faster, both because you can get it from more experts, and because I am checking Statalist more often then my own email

Best, Sergiy Radyakin

PS: wiot_full.dta is one dataset which could have been saved in an older format by the data producer without any loss of data or functionality, but making it more compatible and widening the audience for the data. These are the variable types:

year            int    %9.0g                  
row_country     str3   %9s                    
col_country     str3   %9s                    
row_item        byte   %10.0g                 
col_item        byte   %9.0g                  
value           double %10.0g

And they can be accommodated in Stata 8-9 format, without a problem.

Best, Sergiy Radyakin

[Clyde Schechter]

PS: wiot_full.dta is one dataset which could have been saved in an older format by the data producer without any loss of data or functionality, but making it more compatible and widening the audience for the data.

True. But if I were creating a public use data set from one of my studies, my existing Stata configurations would not enable me to save back any earlier than version 11 format. And even if I did still have earlier versions of Stata lying around, I'm not sure I would always know just how far back I could go without loss of information. I suppose I could serially check the -whatsnew_n_to_n+1-'s going back a while. But I think I'd be more likely to assume that going back two or three versions would reach the vast majority of potential users and save me a lot of work.