I'm not sure they are 'damaged beasts' :o) I use 'child forms' all the time but mostly when I want a free floating form that requires user input and prevents entry into other forms until the user clicks on OK or Cancel. For forms launched from a main form, I mostly use modeless forms and check to see if it is already instantiated before launching it a 2nd time. If it is, I just bring it up on top of all other forms when the user tries to load it again from a menu or a button on another form.



>I took Sergey's pageframe advice and got it running this afternoon. There are still some cosmetic ideas I have in mind to make the page transitions more transparent to the user but it's basically working. Thanks to all, especially Sergey. He deserves an award <g>.
>
>Just out of curiosity now, are child forms more powerful than I suspect or are they damaged beasts?
>
>
>>I'm with Sergey on this. The UT helped me in the past to use a pageframe and set the pages dynamically or show/hide pages. You might want to look at Cetin's code:
>>
>>Re: Hide pages in pageframe? Thread #1014786 Message #1014937
>>
>>I like Craig's example too -hiding the page tab:
>>
>>Re: Hide pages in pageframe? Thread #1014786 Message #1014823
>>
>>in the same thread.
>>
>>
>>>I have just created my first child form. (Bowing deeply). It is partly there, meaning it appears inside the parent form and shows the expected data. However, there are two problems. One is that the parent form's controls become inaccessible, even though the child form is defined as modeless. The other is I can't figure out how to control the placement of the child form within the parent. I want it to be in a specific place, just like it was a control on the form.
>>>
>>>If you're wondering why I am doing this in the first place, the parent form displays one of three different grids depending on choices made by the user. I don't want to duplicate the whole form three times just to have different grids.
>>>
>>>Thanks in advance for any advice.