Hi Knut, Is it possible you can get a test set to us? It would be good to know if the fix for bug 31719 does indeed fix your problem. Mike

Gerton - apstart fixed it! However, I did indeed need to set form focus to the '2nd' form in the stack. Mike - Unfortunately, we seem to be stuck on 9.6.08.... Regards, Knut

Hi Knut, thats exactly the "problem" with nonmodal forms: the edit will not wait until the "structure editor" is terminated by accept/quit/exit as in modal forms and then complete the rest of the exec trigger. So you are immediately executing the rest of the exec trigger and be back on the calling component. Nice day from Frankfurt/Germany, Uli

Hi Uli, Well, yes, you're not telling me something I haven't already observed... Since a non-modal form cannot be activated from a modal form, it would imply the 1st component has to be non-modal... I've tried both a non-modal attached and non-modal detached - doesn't seem to make any difference. I've tried setformfocus - no joy.... So, since we do have the ability to have non-modal components - I must be missing something, somewhere, in order to make Uniface activate the structure editor... Any ideas anyone? Knut

set the focus to the non-modal form after you have activated it

Hi Knut, try the apstart statement. It does exactly what you want: start the Structure Editor or force Uniface to become interactive. Hope that it helps. Gerton

This looks like the reported bug 31719 whereby UNIFACE passes the focus to a hidden form.  Title: "Non-modal form grabs focus and does not allow changing focus to other form". What actually happens is that uniface searches for a first promptable field and ignored that the form is hidden in this bug. Meaning that the prompt is on a hidden tab-form and can in certain cases not pulled away by another form. There is a fix coming soon for this  bug31719. Somewhere in 9.7.05.004 or 9.7.05.005. Hope this helps Jasper