Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!ucsd!dog.ee.lbl.gov!pasteur!agate!garnet.berkeley.edu!bmug
From: bmug@garnet.berkeley.edu (BMUG)
Newsgroups: comp.databases
Subject: Re: <None>
Message-ID: <1990Oct16.213741.9343@agate.berkeley.edu>
Date: 16 Oct 90 21:37:41 GMT
References: <26144.271aec63@kuhub.cc.ukans.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: University of California, Berkeley
Lines: 23

In article <26144.271aec63@kuhub.cc.ukans.edu> 2fmjbeach@kuhub.cc.ukans.edu writes:
>one of the database i wrote have a stack error....yes, i know wht a stack is.
>it is a 4th Dimension database.
>any clue on wht might be wrong?????

The most common reason for stack errors in 4th Dimension has to do with
not properly exiting from a procedure before another procedure is called.
For instance, stacking up successive MODIFY SELECTION commands will eat
up the stack eventually.

Another less common cause would be if recursion were being used
incorrectly.  For obvious reasons, this will eat the stack also.

If you are having this problem often, try calling ACIUS at 408-252-4444
and go over your code with them, or, if you have a Compuserve account,
discuss it with the dozens of 4D developers that frequent the ACIUS
forum.

John Heckendorn
                                                             /\
BMUG                      ARPA: bmug@garnet.berkeley.EDU    A__A
1442A Walnut St., #62     BITNET: bmug@ucbgarne             |()|
Berkeley, CA  94709       Phone: (415) 549-2684             |  |