From | Richard Williams <[email protected]> |
To | [email protected], [email protected] |
Subject | Re: st: Re: aorder: system limit exceeded |
Date | Fri, 01 Jul 2005 00:49:33 -0500 |
At 03:31 PM 7/1/2005 +1000, James Muller wrote:
It's something to do with the updated release of aorder.Good catch. But, instead of trying all these tricks, I would suggest just copying the old version and name it aorder2, and changing the program line accordingly. In general I don't think it is a good idea to try to change the official Stata programs; instead make copies with new names and place them in c:\ado\personal or something like that.
When I run release 2.2.2 found in the 'base' adopath directory of Stata 8 it works fine; the release in the 'update' adopath directory dispays the bug. Since 2.2.2 is not available in Stata9 I have attached the old version to this email; it works fine in Stata9.
A crude way of fixing this, -I believe-, is to copy the old release to update path and change the version numbering so it won't get overwritten. I'm not sure of the mechanics of the update process, but if you trick whatever mechanism is used into thinking the old release is the current, then when the new (corrected) release, "version 2.2.4", is provided then your aorder will automatically update.
© Copyright 1996–2024 StataCorp LLC | Terms of use | Privacy | Contact us | What's new | Site index |