Hi Jingjing,
One way to proceed here would be to try calling your -nlsurweb- program
directly (rather than via -nlsur-) with trace on. This should let you track
down for yourself where things are going awry. (I'm not sure why calling it
via the -nlsur- syntax doesn't give the full tracelog, but whatever the
reason, it doesn't seem to.)
So:
set trace on
nlsurweb [nlsurwebarguments]
If you're unsure exactly what arguments -nlsur- is passing to -nlsurweb-,
you should be able to find them in the trace log from your original call to
-nlsur-.
Hope this helps somewhat,
Glenn.
[email protected] wrote:
Thanks Eva! You are so nice and patient.
After correcting all the typo you mentioned, the codes for the example
works.
However, in my own program, there's r(111) even correcting all the similar
typo. I am not sure if r(11) is still a kind of error that caused by typo or
other big errors. If it's caused by typo, I will check it again and agian
until it works. What I am worried about is that it's the codes designing
errors.
*
* For searches and help try:
* http://www.stata.com/help.cgi?search
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
