Hi Peter,

The only way we resolved the memory leak issue with QBE queries was to 
rewrite everything as LocalSQL. Since then we have never had a problem.

FWIW
Leslie.


On 18/09/2018 2:30 AM, Peter wrote:
> Regarding memory leaks, is there anything that can be done to
> clear/release them? Specifically is there something programmaticaly that
> can be done?
>
> Peter
>
>
> On 09/16/2018 05:24 AM, Steven Green wrote:
>> probably would help to know what the app is doing when the problem
>> occurs.. I think there's still a memory leak when you do a query in a
>> loop, over and over again.. stuff like that.. it might be context, not
>> environment
>>
>>
>> --
>>
>> Steven Green
>> Myrtle Beach, South Carolina, USA
>>
>> http://www.OasisTradingPost.com
>>
>> Collectibles and Memorabilia
>> Vintage Lego Sets and Parts
>> - and Paradox support, too
>> "Mark Bannister"  wrote in message
>> news:5b9bcd01$1@pnews.thedbcommunity.com...
>>
>> We have 10-12 computers running paradox and they are all different.
>> They are all running some version of Win 7.  They all behave
>> differently.  All BDE settings are the same.
>> I have some lower end but new computers that perform pretty zippily
>> until they freeze with "Insufficient memory" errors.  Task manager shows
>> plenty of memory and processor.
>> I don't know enough about Windows to know what to tinker with.  I did
>> increase BDE memsize to 64 (vs 32) on a couple of them and that helps
>> some (maybe, unclear at this time).
>> Any thoughts on what could be causing problems?
>>    --
>> Mark Bannister

---
This email has been checked for viruses by AVG.
https://www.avg.com