I'd like to strength Martin's point.
It's a clear ground rule for all that StataCorp tech-support are not
obliged to answer questions on user-written software (including your
own). They sometimes will indicate anything obvious to them, but as said
there is no obligation.
Although it may not seem so, this is in the interests of almost all. If
you sent an email to tech-support about some detail in Stata that's
bugging you, you would not want doubled response time because they are
trying to make sense of some users' buggy code.
In this particular case, the problem reported does not appear soluble
without much more information.
Roy Wada, the author of -outreg2-, is, or at the very least has been
recently, a member of this list.
If all else fails, David should contact the program authors. Even
experienced user-programmers on this list may be unwilling to try to
guess what may be happening with long and complicated programs like
-outreg- or -outreg2-.
Nick
[email protected]
Martin Weiss
" I've contacted Stata tech support but they have not been of
any help." That is unusual. Probable cause is that you are asking for
advice
on a user-written command.
Anyway, -outreg2- probably generates -tempvar-s along the way, so throw
the
trace on "-set tr on-" and show us the output in the immediate vicinity
of
the error...
David Malison
I'm having a lot of trouble getting the outreg and outreg2
commands to work in Stata (version 10.1). When invoking outreg, I
always get the r(198) error that says "obs must be between" and then
gives an arbitrary range (the lower bound of which is twice the number
of variables in the regression). For example:
sysuse auto, clear
reg price mpg
outreg using auto1
This sequence of commands gives me the following error:
obs must be between 4 and 1167
r(198);
If I use the outreg2 command I get a r(902) error that says there is a
memory problem. To use the previous example:
sysuse auto, clear
reg price mpg
outreg2 using auto1
This sequence triggers the following error:
no room to add more variables because of width
An attempt was made to add a variable that would have increased
the memory required to store an observation beyond what
is currently possible. You have the following alternatives:
1. Store existing variables more efficiently; see help compress.
2. Drop some variables or observations; see help drop. (Think
of Stata's data area as the area of a rectangle; Stata
can trade off width and length.)
3. Increase the amount of memory allocated to the data area
using the set memory command; see help memory.
r(902);
No idea why I would be running into memory problems with this simple
sequence. I've contacted Stata tech support but they have not been of
any help.
*
* 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/
