Mathais,

No bug, you still have two outstanding object refs to o2 held by the collection. An object can not destruct until all references to it are removed VFP has always worked this way.

You can going to have to tell the collection to remove the references, once you do that the form created will destroy and the global memvar will release.

>DEFINE CLASS _Form AS Form
> PROTECTED PROCEDURE Init AS VOID
> PUBLIC gbIamHere
> DODEFAULT()
> ENDPROC
> PROTECTED PROCEDURE Destroy AS VOID
> Release gbIamHere
> DODEFAULT()
> ENDPROC
>ENDDEFINE
>
>Now do this :
>
>o = CREATEOBJECT('Collection')
>o2 = CREATEOBJECT('_Form')
>SET STEP ON * now we see the gbIamHere var in debug-window
>o.Add(o2,'First')
>o.Add(o2,'Second')
>
>o2.Release()
>SET STEP ON * -> o2 = .NULL.;o.Count = 0 this should be so, BUT gbIamHere is still visible -> Destroy has not fired -> internal dangling object-reference
>
>Because I wanted a collection to save same references with different keys this is really annoying !
>We should call this a bug, shouldn't we ?