>>It's actually hard to create a dangling reference, unless you get into some complicated scheme (e.g. two objects keeping references to each other in their properties). If you keep just one reference to it (as in thisform.oSettings), it destroys cleanly, no worries.
>
>But if you create this reference .oSetting (in LOAD or in INIT), don't you have to set it to NULL in Destroy method of the form?

Perhaps, if you are experiencing problems and are chasing phantoms, you do that to get a suspect off the list. But normally, when the form destroys, this reference is gone. Then .oSetting's reference count drops to zero, and it gets released too.