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]

Re: st: stata logfile in Dropbox

From   Red Owl <>
To   <>
Subject   Re: st: stata logfile in Dropbox
Date   Thu, 26 Dec 2013 23:07:02 -0500


I just tried this with my own Dropbox, and it worked fine.
I left a log open for a few minutes and ran several Stata
procedures during that time.

I opened the log file in my Dropbox several times during that
process and was able to see the complete, updated log after
each additional Stata process.

The only difference I can see between my test and yours is that
I have moved my Dropbox away from my C: drive under Windows and
that I am using Windows 8.1.  Since your Dropbox is located in
the default folder on the C: drive, that might cause some write
permission issue.  The C: drive often has permission issues.

Red Owl

> Michael Stewart wrote at Thu, 26 Dec 2013 22:13:00 -0500:
> I was wondering if it is possible for Stata to start a log file in the
> Many time, when I start long jobs(which might take hours), It  might
> be great if I can check output from my smart phone.With this in mind,
> I started a log file in my drop box account. My code is as follows
> I am using Stata 12 .
> Platform: Windows 7
> **************************************************
> capture log close
> cd "C:/Users/mike/Dropbox/_stata_output"
> log using stata.log,replace
> ***************************************************
> The log file starts after the above set of commands are issued but it
> doesn't get updated .
> I always see the following output
> ***************************************************
>       name:  <unnamed>
>        log:  C:\Users\mike\Dropbox\_stata_output\stata.log
>   log type:  text
>  opened on:  26 Dec 2013, 20:43:39
> end of do-file
> ***************************************************
> Any ideas thought are welcome.

*   For searches and help try:

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