Specifing an owner form controls both lifetime and z-order -- two completely unrelated things unfortunately.

The end effect is that the child form cannot be moved in the background behind it's parent but this kind of UI is rare, I can't remember ever seeing it in MS Office for instance except. . . mmmno, not under any occasion.

Then again in the same MS Office opening a couple of documents renders a couple of separate top "unowned" forms so this is *the* familiar behavior users expect from every Windows application IMO.

Looping Forms collection on exit is the norm, using a single (modal) form that can be easily unloaded on exit is the case for (some) utility applications only.

cheers,
</wqw>