Re: Problem with underscore character in variable name
"According to the documentation, an underscore character is allowed in variable names. And, indeed, I have no problem defining new variable names with an underscore and using them in analysis (v2.1.0.151). .... However, when the data have been saved and one opens the file for further analysis, the variable has been renamed v1 (or v2, etc). "
Actually this is a bug in analysis. Will be corrected.
Explicitly _ is NOT allowed. Where in the documentation is _ allowed. This is a misrepresentation.
The reason is : _ is the representation of a string variable in the qes file, but apparently we made an error in the analysis allowing for this on generate. (e.g. gen i abc_d = 1 or define abc_d # )
regards
Jens Lauritsen
In the DEFINE.HTM documentation is written "
Variable names in the DEFINE statement must be 10 or fewer characters.Variable names may not begin with a number or contain spaced, hyphens or other punctuation, although the underline character "_" is allowed. " Annemieke van Middelkoop Pretoria, South Africa
On Sun, Oct 19, 2008 at 9:45 PM, epidata-list@lists.umanitoba.ca wrote:
"According to the documentation, an underscore character is allowed in variable names. And, indeed, I have no problem defining new variable names with an underscore and using them in analysis (v2.1.0.151). .... However, when the data have been saved and one opens the file for further analysis, the variable has been renamed v1 (or v2, etc). "
Actually this is a bug in analysis. Will be corrected.
Explicitly _ is NOT allowed. Where in the documentation is _ allowed. This is a misrepresentation.
The reason is : _ is the representation of a string variable in the qes file, but apparently we made an error in the analysis allowing for this on generate. (e.g. gen i abc_d = 1 or define abc_d # )
regards
Jens Lauritsen
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
participants (1)
-
epidata-list＠lists.umanitoba.ca