Most common cause I've found in code is creating objects and not destroying them.  You say you are clicking on a row and retrieving child rows, are you doing it in another window?  Is it possible you create a ds in the new window and don't destroy it, or another nvo maybe?  Check for any CREATE statements and make sure there is also a DESTROY.  Sometimes it's helpful to put the DESTROY in a finally block of a try/catch so you can be assured you're not exiting out (or erroring out) and missing the destroy.  Any use of arrays, like putting the data into an array?  If so, you can do something like:

String   ls_col1[], ls_null[]  

//populate your array, then finish with

ls_col1 = ls_null

If you are opening another window for the child retrieve, it sounds like that might be where to start looking.

Good luck.

Kevin

It sounds to me like one of the DataWindows might be retrieving too many rows. Perhaps one is retrieving several thousand rows but then filtering it down to a few rows.

Hi Richard;

  For DWO's here is what I do in my code to fully release their memory ...

• DC. Reset ( )
• DC_DataObject = ""

For a DataStore

• DS. Reset ( )
• DS_DataObject = ""
• Destroy

Here is a PB.INI setting that you can try ..

[DataStore Behavior]
; No = do NOT use MS-Window handles in DS processing (Default is yes). "No" gives much better performance!
UseHwnd=no

Regards ... Chris

You didn't say what version of PB you are using.

Creating objects in a loop could use a lot of memory. The GarbageCollect function can be used to release unused objects.

The memory manager will not release allocated memory back to the operating system. It allocates memory as needed and when it is finished with a block of memory, it marks it as free (internally) and will re-use it later.

There might be a memory management option that you can put in a pb.ini file but those aren't publicly documented anywhere except in forum posts.