Dragan --

Back in my DOS days I had a problem similar. Using a drilldown in hierarchical data design to access detail information.

The form used one interface for the navigation. A listbox tracked the history of filters the user chose. The browse showed the various hierarchies. Navigating through levels was simple. The user could create a new filter, pop up a level, or view the detail record at any time. The Web interface with backward/forward movement makes it even more familiar.

I know that's overkill for your situation, but just wanted to mention it.

Jay

>>>>(vfp7 on w2k pro ws)
>>>>
>>>>I have a certain form class whose basic feature is an incremental search (i.e. readonly) grid. The data are somewhat hierarchically organized, so I have one form which searches the top level of documents, has a button which launches the second level search (within a p-view based on selection) and the button on this second form has an add/edit button.
>>>>
>>>>This button hides its form and launches the third form. So far so good, everything is fine. All forms are modal, BTW. Now when the last form exits, it shows the second form and returns the focus to it. The problem is that this active form is behind the first form. Now I know I could just keep them all non-modal, or pass the reference instead of just view parameters etc etc - one of those will eventually work. The question is whether anyone knows a faster way to resolve this. I want the second form to appear as it was before I launched the third.
>>>
>>>
>>>Does a This.Show() on the activate of the second window help?
>
>Nope.
>
>Or set AlwaysOnTop=.T. to the second and third forms...
>
>Second one was enough, thanks. I hope I won't have more than three levels, but I figure I could set it to .f. before launching a modal form and setting it to .t. on return.