[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]
RE: st: Data Entry
"Nick Cox" <firstname.lastname@example.org>
RE: st: Data Entry
Thu, 7 Aug 2008 17:19:51 +0100
I gather that you are implying that this could happen with Stata.
Because when you open a file in Excel that somebody else is changing,
you get a proper warning and can't destroy the other's work.
On 8/7/08, Nick Cox <email@example.com> wrote:
> Sorry, this isn't clear to me: Why is use of a Stata file by two people any more problematic than use of (say) an Access or Excel file?
> Eduardo Palencia Herrejón
> You are probably right, Nick, but when data must be introduced by a
> couple of persons, as is the case, direct data entry into the same
> Stata file becomes problematic. I think the best solution could be a
> friendly form (Access? Epidata?), checking the data at its entry, and
> saving it in a file to be imported to Stata using a do file.
> The data I need to analize are quite simple: most of them are daily
> counts of activity in an ICU.
> 2008/8/5 Nick Cox <firstname.lastname@example.org>:
> > First off, "data entry" may not mean exactly the same to all.
> > Does that mean that you -- or someone else -- is typing data directly
> > into a program?
> > (i.e. data do not already exist as some file or files)
> > Does that mean that data values are checked at time of input and users
> > are prompted immediately for unacceptable values? If the latter, then
> > you may well need something outside Stata.
> > Otherwise, my position on this on this is eccentric: I like using Stata
> > for data entry into Stata. I then have no problems of file readability,
> > conversion, etc.
> > A simple example is trying to re-create problems mentioned on Statalist
> > with example data that people give in their postings. Some combination
> > of data editor, do-file editor, and -split- usually gets their examples
> > into Stata without undue effort.
* For searches and help try: