Too many nested GOSUBS

Kenneth Brody kenbrody at bestweb.net
Wed Dec 20 15:24:47 PST 2006


Quoting Fairlight (Wed, 20 Dec 2006 15:58:36 -0500):

> On Wed, Dec 20, 2006 at 03:37:05PM -0500, Kenneth Brody may or may not
> have
> proven themselves an utter git by pronouncing:
> > > Y'all catch dis heeyah?  Kenneth Brody been jivin' 'bout like:
> > > > It is reset every time you enter update mode.  For example, the
> > > > following will not give you a "too many nested gosubs" error, no
> > > > matter how many times you press "T", even if you don't switch
> > > > records:
> > >
> > > And if you never enter update mode?  If it's just processing sitting
> > > there looping, but changing records?
> >
> > If the process is looping and never ending, how could the gosub stack
> > be reset?
>
> Perhaps we're having a problem with different definitions of "update
> mode"? Define that specifically and if I have further questions, I'll
> post them.

What's not to understand about "update mode" in *clerk?

>From the time you press a key to enter "update mode", whether that be
by pressing "U" and having filePro default to "update", or by pressing
a key with an associated @key event, or creating a record in "add
records" mode, to the time the record is finally saved because all
available processing has ended.

What is your definition of "update mode"?

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com


More information about the Filepro-list mailing list