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: RE: numlabel gives syntax error on one specific dataset

From   Graham Wright <>
Subject   Re: st: RE: numlabel gives syntax error on one specific dataset
Date   Wed, 23 Feb 2011 09:39:43 -0500

Well it didn't work both before and after i updated, ALSO, my coworkers all get the same issue with this dataset. The bizarre thing is that even if I drop all but two variables (the id var and a single labeled numeric variable) the command still doesn't work, no matter what single variable I choose. I can send you (or someone) this trimmed down version of the data set if someone is willing to look at it. But, what could possibly be causing this? Could the file corrupted in some way? It looks totally fine in every other regard.


On 2/23/2011 9:22 AM, Nick Cox wrote:
You are using Mata. -numlabel- uses Mata.

There are at least two possibilities otherwise:

1. Your -update- was incomplete or at fault in some way. Run -update query- to check.

2. Something in your dataset is odd. However, we can't test for the same problem without your dataset.

Either way, if other list members can't diagnose this, it sounds like a problem for tech-support.


Graham Wright

So I've often used the command

numlabel, add force

to make sure I can see the numeric values of the labels of the variable
I'm working with and it usually works fine, but on this one dataset the
command doesn't work.  I get the following error message when I try

nothing found where subexp expected

and r(3000) says that it's a Mata syntax error message, but I'm not
using mata!

I even get the error when I generate the complete syntax using the pull
down menu:

. numlabel, add mask("#. ")
nothing found where subexp expected

But this is only on one specific dataset, On every other dataset I open
the command works fine, so obviously it's not a syntax error, despite
what the error message says. I can't think of anything weird about this
specific dataset that would cause this command to give me a syntax error
there and work everywhere else, but I don't even know where to look.

Anyone have any advice? I'm running version 11 and just updated today,
but that didn't fix the problem.

*   For searches and help try:

*   For searches and help try:

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