>Paul ...
>The crit_form, WindowType - is - set to 1 - Modal.
>However, if you look at this code, it calls up TWO forms. First it has - obasic_info.show which is a form object set up from the - DEFINE class xjfs as jfs_form - section of the code. Then when that form is on the screen, a CommandGroup button on it calls up the 2nd form, crit_form, which also has CommandGroup buttons on it.
>The way this prg - should - work is that the prg a) shows the first form, b) when the user clicks on its button 11, the c) crit_form is shown, d) when the user clicks on any button on the crit_form, it closes (releases)and e) we drop back to the first form window and the Browse should be shown.
>But that doesn't happen.
>
>John
>JF Services

I think Browse inherited its behavior (it's so OOP :) from 2.x, where it opened in currently active window; actually it was a separate window, but you couldn't move it, resize or do anything. It simply covered the active window; now it seems to be covered by the active form.
There was an old Indian trick for this - since Browse uses some window's definition as soon as it finds one, it can also be supplied a window definition. Therefore, you may try

Define Window BrowseTemplate From xx, yy Size ww, hh ... [whatever options you may also want to add]
Do form ...
Browse Window BrowseTemplate

The BrowseTemplate window need not be activated at all, nor visible - it's just used as a template. Remember to release it - user defined windows seemed to have a global scope, so once they are defined, they lived until released, and knowing compatibility issues, they still do (this means I haven't tried it thoroughly, I just seem to remember it works this way).