Ed,

SYS(1016) has never been a reliable memory use indicator in VFP, if you are instantiatng and destructing objects.

>Now, I've got a different puzzle for you. Try the code out below, running it 'as is' first. Then, uncomment section B and try it again. Next, uncomment section A and try it. Finally, uncomment section C and try it. Section B doesn't cause a memory leak, but sections A and C do.
>
>Note: This is in VFP 5.00.00.0402. I thought I had implemented SP3, but evidently not. I'm going to retry this exercise after applying the service pack.