Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at

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

Fwd: st: esttab into Excel tables that are directly readable?

From   Jen Zhen <>
Subject   Fwd: st: esttab into Excel tables that are directly readable?
Date   Fri, 18 Oct 2013 14:05:41 +0200

Dear Sergiy and David,

thank you for your replies regarding my misgivings about -esttab-.

On -esttab-:
By "extra clicks" I meant the "Text to Columns" step mentioned by
David: When open the CSV file in Excel, either by clicking on the
hyperlink with its name right in the Stata results window or by
opening the saved file in Windows Explorer, I see all data in a single
column and first need to tell Excel that at each comma the data are to
be split into separate columns. It would be convenient if I could
esttab into a format which Excel does then directly display in
separate columns, but I have not been able to find such an output
format for esttab. I am still running Stata 11 and currently have no
financial resources to upgrade to a later version.

On -outreg2-:
I have thus been considering to switch from -esttab- to Roy Wada's
-outreg2-. However, here I find it disadvantageous that I cannot just
compile the table with one line after all the regressions but must
instead use a separate -outreg2 ..., append- after each regression. I
can build that into a loop.
But it seems that I can only prevent -outreg2- from adding all earlier
regression results run in that Stata session, I need to separately
-outreg2- my first regression with the replace option and then all
others with the append option. But that looks very inelegant in my
dofile. Do people know any more elegant way of doing this?

Thank you so much and kind regards,

On Tue, Oct 8, 2013 at 11:35 PM, Sergiy Radyakin <> wrote:
> Jen,
> CSV stands for "comma separated values". not "formats". any formatting
> you wish to apply that is not applied by Excel automatically - you
> will have to add it manually. The full list of automatic formatting is
> unknown [to me], but Excel usually trucates numbers that are longer
> than 15 digits, and may convert values with dashes or slashes to
> date/time formatted values.
> For me as a non-native speaker what does "..need some extra clicks to
> put Text into Columns." mean? Do you need to put particular titles
> into the column headers? Or do you need to format columns as "text"
> not "numeric"? Or do you mean to adjust alignment of the columns? Or
> something else? Just in case, for importing files into Excel in CSV
> format, the following page is very interesting:
> StataCorp has added the classes for handling tables still in version
> 12, which support column titles, widths, formats, coloring,
> separators, etc. And they are used for many "standard" outputs we see
> on the screen - regression output, matrix output, summarize output,
> etc.
> Given the recently added export to Excel, and a plethora of the output
> commands estout, tabout, esttab, latab, outtex, outreg2, outtable,
> texdoc I would be surprised if there is no output to _formatted_ Excel
> tables in Stata 14 (if it is not in Stata 13 already).
> Best, Sergiy Radyakin.
> On Tue, Oct 8, 2013 at 4:18 PM, Jen Zhen <> wrote:
> > Dear listers,
> >
> > I've forever been using Ben Jann's -esttab- command to get my
> > regression tables into Stata. I quite like that I can do all
> > regressions as I like, just needing to put an "eststo:" in front, and
> > then just need the one line to get the table.
> >
> > The one thing I find annoying is that when I tell Stata to -esttab
> > using table.csv- and then open that table in Excel, I always need some
> > extra clicks in Stata to put the Text into Columns. So I'm wondering
> > whether there is any way to esttab tables that I can open and directly
> > read in Excel?
> >
> > Thank you so much and kind regards,
> > JZ
> > *
> > *   For searches and help try:
> > *
> > *
> > *
> *
> *   For searches and help try:
> *
> *
> *
*   For searches and help try:

© Copyright 1996–2018 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index