Problem is, -compress- crashes on these 'oversize' strings too (like -list-
or -drop-). The only way I found to handle this is to generate a new
variable using substr function, but those extra blanks shouldn't be there in
the first place...
Daniel.
-----Original Message-----
From: Elizabeth Allred [mailto:[email protected]]
Sent: Tuesday, January 21, 2003 1:17 PM
To: [email protected]
Subject: Re: st: Stata 8 - ODBC utility
The way to 'squeeze' out the extra space is to use _compress_
"Grochulski, W. Daniel" wrote:
>
> Dear Listers,
>
> While happily navigating my freshly installed Stata 8 (running under
> Windows 2000) I was stopped by seemingly odd behavior of the ODBC utility
> (one of the goodies in Stata 8). Loading tables via -odbc- is just a snap,
> there is, however, something wrong with the way the string variables are
> handled - my Stata consistently adds a 127 blank characters pad to any
> downloaded string variable, so i.e. 20 characters string is loaded and
> reported as having 147 characters (str147). This happens with both
> SQL-server and MS Access databases - below I reproduce results of the load
> from "Northwind" database to be compared with printouts given in Reference
> Manual for -odbc-. Since all these 'strxxx' strings are longer than 80
> characters Intercooled Stata can handle, this dataset is exploding into
> user's face when trying to -list-, -drop- or -keep- (Stata crashes and
> exits). One can of course extract the original strings by generating
> properly defined new string variables using substr function, but this is a
> bother (and you have to keep the 'oversized' string variables anyway).
>
> Any suggestions?
>
> Daniel
>
*
* 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/
*
* 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/
