![]() ![]() But this is usually because users have not upgraded Ben Jann's palettes package, etc. I sometimes get queries that packages have broken down. For example, if a program calls another program, then, it should flag the user if he/she is using an older version of an already installed program and should upgrade it. (See the -retainlbl- help file for further detail.)Ĭan we have version checks for user-written or SSC programs please especially when programming ados. ![]() I frequently prefer to keep the same unchanged variable label or to add my own prefix or suffix to the existing variable label. Vce the file was created with a newer version pdf#The PDF documentation for -reshape- is also silent on labels, while that for -collapse- says " collapse adds meaningful variable labels to the variables in this new dataset." I don't like Stata's version of a "meaningful" variable label. In all versions through 17, the word "label" is absent from both help files. This approach is consistent with -reshape-'s use of variable -characteristics- and global macros to store information on the -reshape- so that it can be reversed.īy the way, the help files for -reshape- and -collapse- could be improved by describing how these two commands deal with variable and value labels. Then the user would again run -retainlbl- after completing either -reshape- or -collapse- to restore the variable labels, or perhaps slightly modified versions of those labels. Code: view net describe retainlbl, from()I designed version 2.0 of -retainlbl- to be run on the variables prior to executing either -reshape- or -collapse-, which would store the variable labels with the variable names in global macros. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |