>>The only trouble is your wish for it to have a fixed position. The users have got this habit to move windows as they like, and if you create a form which can't move, they'll be at least somewhat confused, or maybe even pis*ed off.
>>
>>As for the general role of child forms in a MDI form, I haven't found use for them yet, not in a VFP app. Even in one case where I have an OCX editor within the app, the editor's window(s) reside(s) in _screen. This doesn't mean there isn't an app which would benefit from a MDI, just means I didn't write one yet.
>
>
>Again, my objective was to display multiple grids in the same place on a form. I wanted it to act just like an ordinary grid on a form, except the ControlSources need to be different. For some reason child forms came to mind. Sergey's suggestion of a pageframe is cleaner and certainly easier.

So we're actually looking for a good case where child forms may be usable. This one was obviously easier to do within a single form.

I imagine an app which handles multiple entities connected over a single document may use child document approach - say, a multi-party contract, where you may want to have parties and the contract within one window, then another contract in another window (with its child windows for its own parties and text of contract). Or a process controlling app with each process as its own MDI form with components in their own child windows.