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 I did here was to implement "form modal" forms .
>when a form needs a child form it CREATEOBJECT the new form, move the focus
>to that form and then doesn't allow the focus to return to it as long as the child form is open
>when the child form terminates it sends a message to the parent form that resumes the operation that was going in (so what I actually have is 2 methods one that is called before the child form is shown and one that is called when it terminated)