I have observed this "memory not released" problem occurs when ANY EEP is
executed in a form (on a field or on the row), as well as various other
places. Look at values for (ISTAT('MEMORY')) & (ISTAT('TOTALALLOC')) before
& after using a form, or just calc & display those values in the EEP and
watch how they change. I test for resulting values of these 2 ISTAT
parameters and do the "ZIP RETURN..." if the "memory" gets below a specified
level or the "totalalloc" gets above a specified level. I use 10,000,000 as
the specified levels, but it will depend on installed memory, etc. that you
are using.
Frank Radice
[EMAIL PROTECTED]
----------------------------------------------------------------------------
---------------
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 28, 2001 11:05 AM
To: [EMAIL PROTECTED]
Subject: Re: RE: Novell Tuning for RBase
We have evidence that it occurs just [F8]ing through a form with a couple of
update eeps - it never frees up the memory. Also open and close a form, and
the memory used by the form does not free up.
[EMAIL PROTECTED] wrote:
>
> Yes I've also seen this problem. �The only moderately educated guess I
have
> is that this occurs when using large iteration loops.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Albert Berry
> Sent: Thursday, June 28, 2001 11:19 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Novell Tuning for RBase
>
>
> We have a caveat for dos sessions under w2k - we have had to add zip
returns
> to the code to free up memory when running rbdos on w2k. The memory in use
> keeps increasing until w2k shuts the machine down.
>
> We suggest that, if you are using rbdos, you fire up a session on w2k
along
> with the monitor and watch the usage climb as you navigate through your
> system.
>
