http://blogs.msdn.com/calvin_hsia/archive/2005/01/20/357388.aspxVFP stores user defined names such as variable, field, property, class and procedure names in a table. When the name table runs out of space, the GC begins. All the entries are marked as unused. Then all the various name table clients are sent a messageen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/calvin_hsia/archive/2005/01/20/357388.aspx#362529Fri, 28 Jan 2005 17:25:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:362529Gunnar PhilippHello Calvin <br> <br>1st i want to thank you for clearing up a few things the vfp-community has been dying to know for a while. i constantly see discussions about items like 'the m dot thingy' or the garbage collection. <br> <br>your test code is very interesting and educational (i had to change the number of variables created from 5000 to 2000 as i work with vfp6. <br> <br>now, i got a question: is it possible to clear that name-table; to release all unused entries? <br> <br>i tried several different release mechanisms like 'release all like x*', etc, but no success. <br> <br>i got a feeling there is no way. if this is correct, would that be a functionality to add to any future advancement made to vfp? <br> <br>again, thanks for your educational blogs.http://blogs.msdn.com/calvin_hsia/archive/2005/01/20/357388.aspx#552235Wed, 15 Mar 2006 23:40:47 GMT91d46819-8472-40ad-a661-2c78acb4018c:552235Calvin Hsia's WebLogIn this post: Heartbeat: Garbage collection in VFP and .NET are similar, I talked about how the VFP name...http://blogs.msdn.com/calvin_hsia/archive/2005/01/20/357388.aspx#8381839Fri, 11 Apr 2008 22:55:30 GMT91d46819-8472-40ad-a661-2c78acb4018c:8381839Calvin Hsia's WebLog<p>Writing programs using .Net is very productive. One reason is because much of memory management is “managed”</p>