Hi Ed,

I think that Vlad G. gave you lots to think about.

My way of looking at it is that your little test may not be valid - depends on why/when VFP elects to do "garbage collection".
I think there is sufficient indirect evidence to conclude that VFP does, indeed, keep its RAM organized the way it need it, including cleaning up.

Are there no implications regarding the Citrix management, or possibly the application's termination mechanism??

Good luck getting to the bottom of it,

JimN

>I'm hoping someone knows how to force VFP to do garbage collection.
>For example, on an NT machine with task manager watching the VFP memory allocated, I type:
>
>x = space(16777184) ' VFP allocates between 20-36meg of RAM
>x = Null
>Release x ' RAM stays allocated
>
>CLOSE ALL
>CLEAR ALL ' No luck - still allocated
>
>Is there any way to force memory allocation? SYS(3050) has
>no effect on this kind of memory allocation.
>
>We have a citrix box with many VFP apps running, and if one
>user runs a VFP routine which needs RAM, the RAM is staying
>allocated to that user indefinitely, slowing the other users
>down.
>
>If anyone has any insites, I would be very thankful.
>
>TIA,
>Ed