>>What did you find out after implementing this trick?
>>BTW, adding call to this procedure from multithreaded VFP dll in each 50 iterations made no effect in our case.
>
>My vague memory is that Bernard's trick didn't really help, though I don't remember for sure.
>
>I added code to the app that lowers its overall memory load by doing some garbage collection and so forth. (We have a bunch of collections that tend to grow and grow and grow.) We got it down to the point that it hasn't been a problem for the customers.
>
>Tamar

The class I'm working on does not use collections at all. It uses a few arrays and it also passes big strings in and out. Also it calls sqlexec (as a method) in a loop. I'll try to comment sqlexec calls and see if it helps to memory. If yes, then I have a plan of how to re-write this dll to use local cursor. If not, then I think the path should be to re-write this dll in .NET