On Thu, 31 May 2001, Jeremy Wadsack wrote:
> > Still, my question hasn't been answered. How can I determine which
> > report is being processed when I hit the memory error?
>
> I don't know that you can. I'd be surprised that the problem is in the
> actual report generation, the memory error usually comes during data
> collection, unless you have just enough memory to hold the data and
> the extra for building reports is the 'straw.'
>
Sorting can use a not-insignificant amount of memory for a long
report. You might want to reduce the length of some of your reports.
You can guess which report is causing trouble by seeing how far the
program got writing the output file before it failed. It should be one
shortly after that that is causing the trouble.
--
Stephen Turner [EMAIL PROTECTED] http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"Ad infinitum, if not ad nauseam." (Interviewee, BBC Radio 4)
+------------------------------------------------------------------------
| This is the analog-help mailing list. To unsubscribe from this
| mailing list, go to
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| List archives are available at
| http://www.mail-archive.com/[email protected]/
| http://lists.isite.net/listgate/analog-help/archives/
| http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------
