Bookmark and Share

Notice: On March 31, it was announced that Statalist is moving from an email list to a forum. The old list will shut down at the end of May, and its replacement, is already up and running.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: st: -save- a varlist

From   Nick Cox <>
Subject   Re: st: -save- a varlist
Date   Tue, 30 Oct 2012 14:23:43 +0000

Note also -label save-.


On Tue, Oct 30, 2012 at 2:21 PM, Austin Nichols <> wrote:
> Jeph Herrin <>:
> And if you do that twice, the -nolabel- option can be used one of
> those times, so you have both values and value labels. But why can't
> you save the whole file locally, if you are allowed to save several
> variables locally?
> On Tue, Oct 30, 2012 at 10:17 AM, Nick Cox <> wrote:
>> As Daniel Feenberg underlined recently, you can -outsheet- part of the
>> data. In the same vein, -outfile- is another alternative.
>> Nick
>> On Tue, Oct 30, 2012 at 2:10 PM, Jeph Herrin <> wrote:
>>> I have a very large dataset (20gb) that I must access remotely, so that
>>> -use- and -save- each take about 30minutes. When I have this file open,
>>> I would like to create some secondary files that contain only 1-3 variable.
>>> If the file were smaller, I would typically use -preserve-, -keep-,
>>> -save-, -restore- to do this. However, this takes a couple of hours. So
>>> I am using
>>> . export excel var1 var2 var3 using file.xls, replace
>>> Then later using -import excel- to read them back in. This is much
>>> faster, but has the obvious drawback that variable labels and other
>>> attributes are lost. It is also aesthetically unsatisfying.
>>> Can anyone suggest an alternative?
> *
> *   For searches and help try:
> *
> *
> *
*   For searches and help try:

© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   Site index