Rob,
thanks for the reply...
I created a test app as you suggested, and it did what it
was supposed to, allowing me to alternate focus from the
parent to the child form...
However, there's nothing unusual about the app in
question, the main form is a treeview/listview pair with
a "settings" button that launches the child form using
Form.Show()...
The child form contains various controls (textboxes,
buttons, a monthcalendar control, and a statusbar), and
the only custom constructor (if you can call it that)
accepts a string value that is used to initialize a
textbox in the form...
I'm still clueless about what could be preventing the
child form from being modeless...
thanks for any more suggestions,
vince
-----Original Message-----
You must have some other code in there causing this,
because Show() createsa modeless window.
We'll need more information in order to help you. (PS:
don't email me theinfo, type it here in the group so everyone can benefit
from the discussion.I don't reply on this email account) Try create a new
blank windows formapplication with Form1 and Form2.
Place a button on Form1 that creates a new instance of
Form2 and calls theShow method, and you'll see that it's not modal.
-Rob [MVP]
"vince" <vl******@sdcera.org> wrote in message
news:06****************************@phx.gbl... I have a windows app whose main dialog contains a
button that launches a form. I've tried using Form.Show() to
have it launch as a modeless form, but it behaves as if
it's modal (i.e. parent form can't receive focus)...
Can someone tell me what I need to do to make the child
form modeless..??? I want to be able to alternate focus
between both dialogs...
thanks,
vince
.