Stata The Stata listserver
[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

[no subject]



--------------------------------------------------------------------------------

It is not clear what format the data are in, but if 9(13) means a pure
numeric format with 4 digits after the decimal (or some other decimal
format), and you don't literally mean a number like 9(13), then the
problem
may be one of precision.  You should probably infix it as a string and
then
use destring, but you may also import the number as a double instead of
the
default float, which would give you more digits of resolution.

Michael Blasnik
michael.blasnik@verizon.net 


----- Original Message ----- 
From: "Rima Chakravarty" <Rima.Chakravarty@dornc.com>
To: <statalist@hsphsun2.harvard.edu>
Sent: Friday, October 01, 2004 8:38 AM
Subject: st: Fwd: Infix Command


> I am trying to import an ascii file into Stata using the infix
command.
> There are fields which has the format as 9(13), without any decimal
> place but numeric. Stata is messing up the last two numbers of that
> specific field in the imported Stata file. But if I import that field
as
> a string field then it is importing it correctly. I have been trying
to
> figure out why this is happening for quite sometime.  Just wondering
if
> anybody have an answer for this.
>
>
>
>
> Rima Chakravarty
> Economist
> Tax Research - Dept. of Revenue
> State of North Carolina
> 919.733.7738



*
*   For searches and help try:
*   http://www.stata.com/support/faqs/res/findit.html
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/



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