>>I would be interested in knowing the answer to this question: Which objects in the base class library do not get destroyed properly when you close a form? I spent this weekend looking at a problem on a form which wasn't running its Unload() method when you closed the form from the Close Box. It turned out that two label objects and two other objects on a page frame were not being destroyed when the form closed, thus preventing Unload() from firing. When I forced the destroy within the destroy method of the page, it worked fine. (The two other objects were child classes of the base class TextBox.)
>>
>>Ed
>
>Ed,
>
>Which version of VFP are you using? If you type ?VERSION(1) you will get eh build number burried about three ro four decimals out mine is 0415, which is the VS SP3 patch.
>
>The only time I have seen objects not get released is when there are errant references that I have failed to clear left around.

Jim,

I'm using the 0402 build. I thought I had applied SP3 to it, but evidently not. Do you find this build to be more or less stable than the last? The developer at my client site has the 0415 build, and his application, and even VFP, crash several times during the day.

You mention errant references to objects...can you elaborate a little on that point? I don't believe I'm referencing an object after it has been destroyed. The only times I've seen this is when the form doesn't unload because some of its objects are still around. Code in the form methods would try to reference objects within a container that no longer existed.

Thanks!

Ed