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: unrecognized command: _anovaparse

From   Nick Cox <>
To   "''" <>
Subject   RE: st: unrecognized command: _anovaparse
Date   Thu, 17 Nov 2011 17:42:00 +0000

Yes; I imagine so. I am only familiar with networks in which only one person can -update-, which can cause different kinds of frustration. 


-----Original Message-----
From: [] On Behalf Of Tim Evans
Sent: 17 November 2011 17:12
To: ''
Subject: RE: st: unrecognized command: _anovaparse


You were right. I use Stata installed over a network. When I did -update all- I wasn't aware of other users preventing access to certain files. Having asked other users to close Stata down momentarily, I have successfully updated and I no longer get the error message. I guess this is the problem you will face with a network install and while it was manageable for me to find the other user(s), this might not be easy for everyone with a network installation.

Best wishes


-----Original Message-----
From: [] On Behalf Of Nick Cox
Sent: 17 November 2011 16:40
Subject: Re: st: unrecognized command: _anovaparse

Despite what you say, this sounds to me like a side-effect of an
incomplete -update-.

_anovaparse is a non-documented official command.

Do look again at the results of -update query-.

(Please don't start new threads by replying to previous messages and
not deleting them, as is explained in the FAQ.)


On Thu, Nov 17, 2011 at 4:34 PM, Tim Evans <> wrote:

> I am using Stata 11.2, and was using the following code to run an anova test:
> webuse systolic
> anova systolic drug
> but I get this error message:
> unrecognized command:  _anovaparse
> r(199);
> Tried to google to see what this meant, but found literally nothing from the search! Any ideas?
> I've tried
> -update all- but this doesn't solve my problem.

*   For searches and help try:

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