Look at any EEP's that you have in the form. Try using the ISTAT('MEMORY')
function (in the EEP or after exiting the form) to report memory info to
help pinpoint a problem EEP or form. See if the memory values change each
time the EEP is executed or the form is used. The memory related ISTAT
parameters work in RB6.5++ (DOS) but don't return meaningful results (or
sometimes crashes) under RB6.5++ (WIN).
You can also check periodically for the value of 'memory' and if it gets too
low, release memory as shown in the following example:
IF (ISTAT('MEMORY')) < 10000000 THEN
ZIP RETURN yourcomspec /C EXIT
ENDI
Thus, you don't need to discover exactly what is draining the memory because
you can "fix" it with code similar to the above.
Frank Radice
[EMAIL PROTECTED]
----------------------------------------------------------------------------
-----------------
I run into the same problem with RBase and Win2k (as do many others on the
list). What happens here is that RBase eats up memory until the computer
hangs/crashes. I've noticed the problem to be much worse on a Celeron
processor machine, but have no insight as to why that would be. I don't
have any help to offer you other than sympathy in that I feel your pain.
----------------------------------------------------------------------------
---------
>
> I seem to be experiencing an inordinate number of crashes in RBase. It all
> seems to revolve around forms, I use them extensively as menus,
> entry forms,
> in eeps, etc.. I can have a form run 30 times in a row with no problem and
> then crash the next 30.. I have tried removing BLOBs, moving look up
> variables to the command file calling the form, closing the form menu and
> using switch/case, etc. etc.
>
> I am running RBW 6.5++ on Windows 2000 Professional, SP2..
>
> I have a nice drwatson log to look at, but it means nothing to me..
>
> I even tried running on a different machine - no difference.
>
