>>Hi, everybody!
>>
>>I've just found very annoying thing. I'm calling MSSQL stored procedure to get 200 character length value from the server. It's being done inside the loop and I see memory leak - the same 200 bytes per call. The code below, when executed, eats 20M of memory. It can be monitored by Windows Task Manager, and the only way to release memory is quit VFP. Nothing else helps. Here's the code:
>>
>
>My tests show that there's 256 bytes memory leak per every parameter passed by reference regardless of the size of data returned. You can change SP to return data in a cursor instead. It would be slower but eliminate memory leak.
Yeah, I've already found that workaround. Moreover, it doesn't seem to be slower. Anyway, spasibo for the idea :)