William,

FYI, the memory leak issue when printing windows reports
on SCREEN was FIXED in TGRB2000 (ver 6.5++), Build: 1.842,
released on June 15, 2001.

Technically, reports with no sorting did not show the same
behavior. Our Dedicated and Talented R:Team fixed that long
time boo-boo by allocating a sort buffer up front and use
the same buffer until R:BASE exists rather than allocate
and free each and every time the report is printed.

Very Best Regards,

Razzak.

At 09:14 AM 8/30/2001 -0700, William Mason wrote:

Don't know about a patch, but two areas that will eat memory like PEZ: Unoptimized WHILE loops (set WHILEOPT OFF in any file with a WHILE in it and it seems to be VERY stable in the latest version) Printing reports - this takes chunks of memory, and doesn't give it back until the end of the RBase session. Especially when printing reports to the screen...
===================================-============================
R:BASE Developers's Conference: http://www.rbase.com/conference
Official R:BASE List Server: mailto:[EMAIL PROTECTED]
RBTI Events/Training: http://www.rbase2000.com/events
R:DCC Members: http://www.rbase2000.com/rdcc
================================================================
R:BASE, Oterro & R:Tango are registered trademarks of RBTI.
==================================-=============================

Reply via email to