>Arnon,
>
>An approach of this I've settled on is for the child form launching object, either a button, or "browseresque label" passes a reference of itself to the child form, the child form then disables the object and reenables it during it's destruct. That way they can't launch two instances of the child form and get themselves confused, but they can still get back to the parent form and work back and forth. So far the client is pretty happy with this "non-modal modality" *s*
>

what we did is to duplicate the win98 interface , so among other things is we have a taskbar - this makes the "form modality" important since when you click on a form's name in the task bar you get to the "modal" dialog instead of the form itself
If you don't need this, then you can probably use your approach which is probably simpler to code


Arnon