Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-ses!hpcuhb!hpindda!keithb
From: keithb@hpindda.HP.COM (Keith Broussard)
Newsgroups: comp.databases
Subject: Re: dBASE IV bugs
Message-ID: <3520003@hpindda.HP.COM>
Date: 14 Jul 89 17:32:31 GMT
References: <10889@trlsasb.oz>
Organization: HP Information Networks, Cupertino, CA
Lines: 24

Oh boy, I have had a real time with the "Insufficient Memory" error
too.  But first, let me comment on your first problem (@M).  This is a
known bug by A-T and there is information about it and a workaround in
the DBASE4 area of the A-T Support BBS (You can get the number by
calling the A-T support line and listening to the recording.  I have
not had this problem, so I don't remember the details, but I remember
reading it.

Now, I talked to A-T support too about the Insufficient Memory error
and was  told that dbase4 will report Insuf Mem when it runs out of
its own internally allocated memory, so that message doesn't
necessarily mean that you ran out of RAM.  Try playing with the
BUCKETS parameter in the CONFIG.DB file.  I have a relatively large
application that would fail during deep nesting or VALID function
calls, and I increased BUCKETS to 4 and the problem seems to occur
much less often.  There are some more parms that you might read about:
these parms allocate MVAR space, etc, but it sounds like you might
need more BUCKET space.  I am still playing with those parameters, but
it appears to be helping.

Let me know what happens, please.  Good luck to you.  I must stop now
because I have insufficient memory to complete this message!

Regards!