Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: Re: Stata won't recognize a user written command


From   Jonah Rexer <[email protected]>
To   [email protected]
Subject   st: Re: Stata won't recognize a user written command
Date   Wed, 12 Feb 2014 09:32:15 +0300

Hello,

A colleague sent me the ado file user-written command, "getreg," that
he wrote. it is an important piece of code in a do file we are
running. I downloaded the ado file, looked up the ado directory using
sysdir, and saved it into a directory that stata recognizes. In fact,
I tried saving it into every possible different folder recognized by
sysdir. When I run the do-file, stata still doesn't recognize the
command. But when it returns the error message, it says "unrecognized
command: numformat," which is not the name of the command, nor does
"numformat" ever even appear in the do file. When I type the command
itself alone into the command box, it seems to recognize the command,
because it doesn't return the "unrecognized command" error message.
But in the do-file the command, "getreg' is not appearing in blue, and
I can't run the do file. I have no idea why this is happening, can
someone help solve this problem??

Thanks,

Jonah

On Wed, Feb 12, 2014 at 9:22 AM, Jonah Rexer <[email protected]> wrote:
> Hello,
>
> A colleague sent me the ado file user-written command, "getreg," that he
> wrote. it is an important piece of code in a do file we are running. I
> downloaded the ado file, looked up the ado directory using sysdir, and saved
> it into a directory that stata recognizes. In fact, I tried saving it into
> every possible different folder recognized by sysdir. When I run the
> do-file, stata still doesn't recognize the command. But when it returns the
> error message, it says "unrecognized command: numformat," which is not the
> name of the command, nor does "numformat" ever even appear in the do file.
> When I type the command itself alone into the command box, it seems to
> recognize the command, because it doesn't return the "unrecognized command"
> error message. But in the do-file the command, "getreg' is not appearing in
> blue, and I can't run the do file. I have no idea why this is happening, can
> someone help solve this problem??
>
> Thanks,
>
> Jonah
>
>
> On Tue, Feb 11, 2014 at 11:51 PM, Jonah Rexer <[email protected]> wrote:
>>
>> Hello,
>>
>> A colleague sent me the ado file user-written command, "getreg," that he
>> wrote. it is an important piece of code in a do file we are running. I
>> downloaded the ado file, looked up the ado directory using sysdir, and saved
>> it into a directory that stata recognizes. In fact, I tried saving it into
>> every possible different folder recognized by sysdir. When I run the
>> do-file, stata still doesn't recognize the command. But when it returns the
>> error message, it says "unrecognized command: numformat," which is not the
>> name of the command, nor does "numformat" ever even appear in the do file.
>> When I type the command itself alone into the command box, it seems to
>> recognize the command, because it doesn't return the "unrecognized command"
>> error message. But in the do-file the command, "getreg' is not appearing in
>> blue, and I can't run the do file. I have no idea why this is happening, can
>> someone help solve this problem??
>>
>> Thanks,
>>
>> Jonah
>>
>> --
>> Jonah Rexer
>> Research Fellow
>> BRAC Uganda
>> Plot 90, Busingiri Zone, Nyanama
>> Kampala, Uganda
>> www.brac.net
>>
>
>
>
> --
> Jonah Rexer
> Research Fellow
> BRAC Uganda
> Plot 90, Busingiri Zone, Nyanama
> Kampala, Uganda
> www.brac.net
>



-- 
Jonah Rexer
Research Fellow
BRAC Uganda
Plot 90, Busingiri Zone, Nyanama
Kampala, Uganda
www.brac.net
*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/faqs/resources/statalist-faq/
*   http://www.ats.ucla.edu/stat/stata/


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