Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: st: Truncated string observations from CSPro
From
"Donovan, Kathleen" <[email protected]>
To
"[email protected]" <[email protected]>
Subject
RE: st: Truncated string observations from CSPro
Date
Mon, 11 Feb 2013 22:05:51 +0000
Some may be longer than 244 but it is importing the observations as a str8, for example. How did it choose str8 for that variable? Furthermore, it is not uniform across the cspro field notes being imported. They range from str8 to str15.
-Kathleen
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Nick Cox
Sent: Monday, February 11, 2013 4:49 PM
To: [email protected]
Subject: Re: st: Truncated string observations from CSPro
One kind of truncation could be that no version of Stata allows string variables longer than 244 characters. See -help limits-. Perhaps you are referring to something else, but let's exclude that as a possibility....
Nick
On Mon, Feb 11, 2013 at 8:36 PM, Donovan, Kathleen <[email protected]> wrote:
> We are getting truncated string observations when we bring data field notes from a CSPro database. We are not sure which program is causing the problem either; CSPro or Stata. Looking at the CSPro-created dictionary, I cannot tell what is determining string value length. This is automatically created and I don't know how to systemically edit it to tell stata which string fields should be longer. Anyone else have this problem or know what causes truncated string values?
>
*
* For searches and help try:
* http://www.stata.com/help.cgi?search
* http://www.stata.com/support/faqs/resources/statalist-faq/
* http://www.ats.ucla.edu/stat/stata/
*
* For searches and help try:
* http://www.stata.com/help.cgi?search
* http://www.stata.com/support/faqs/resources/statalist-faq/
* http://www.ats.ucla.edu/stat/stata/