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: Problems reading in comma separated files

From   Orian Brook <>
To   <>
Subject   RE: st: Problems reading in comma separated files
Date   Fri, 10 Jun 2011 16:50:46 +0100

Thanks Ronán. I guess that I might have to resort to using Access - I've
tried using filefilter to get rid of the dodgy characters, but it doesn't
seem to be doing the job - when I view invisibles there are more of them
still there, although hexdump says not. I could use a text editor to resave
the files, but then I might as well just do the job in Access ...

-----Original Message-----
[] On Behalf Of Ronan Conroy
Sent: 10 June 2011 15:39
Subject: Re: st: Problems reading in comma separated files

On 2011 Meith 10, at 15:01, Orian Brook wrote:

> In Stata 10/SE using insheet, the file is correctly identified as having
> variables, but the column headings are not read, and if you browse the
> it shows all cells as blank except the first, which reads ?ÿþt?. 

That's not ASCII, it's NASTII. 

I have come across cases before where non-ASCII characters cause premature
end to input. The most hideous is the NULL character which, as you might
imagine, is utterly invisible under normal conditions. 

At the very least, open the files and view invisibles. 

If you have a text editor, you can simply convert the files to ASCII.
BBEdit, which I use, has a command that replaces non-ASCII characters with
ASCII ones. 

Ronán Conroy
Associate Professor
Division of Population Health Sciences
Royal College of Surgeons in Ireland
Beaux Lane House
Dublin 2

*   For searches and help try:

*   For searches and help try:

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