Dan, if it stops tracing, you may have an inadvertent low FILES setting. Try adding SET FILES 30 at the top of the first calling procedure and see if that stops the dumps. I have found that R> dumps usually result from returns that cannot find the calling procedure.
Dan Champion <[EMAIL PROTECTED]> wrote: > > >>Hi, > > � I have an application that started crashing on occasion a few months >ago. It is very deep in the process of the code, and I cannot seem to >determine the cause. > � I have used trace, but it always stops tracing before it gets to that >point. �I have tried to determine if there are variables being re-typed >improperly, but don't see that either. > � Any ideas what else I might look for? The process always crashes (dumps >the user back out to the R:> instead of returning to a menu, after the same >set of events, At that point there are nearly 200 variables �that are in >use, and are all typed correctly. > >Thanks in advance, >Dan > > > > >Dan Champion >P.O. Box 223 >Grandville, MI. 49428-0223 >www.championsolutions.net > > -- Albert Berry Full Time Consultant to PSD Solutions 350 West Hubbard, Suite 210 Chicago, IL 60610 312-828-9253 Ext. 32 __________________________________________________________________ The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
