Fake Dialogs using ShowDialog(OwnerForm Form)

[scott blood]

Hello,

We currently have an application that has a lot of screens that allow users
to add new data to the system. These forms are currently accessed via a
browse form, such as the employee's browse form. The user would access the
Add Form by clicking on the Add Employee Button.

Unfortunatly when you use MyForm.ShowDialog(this), the entire application is
locked out, which is the default and accepted behaviour of Windows Forms.

However, i need the ability to only disable access to the browse form that
has called the Add screen and ensure the rest of the application stays
responsive.

I have tried quite a few ways of doing this, but none of them are effective
enough. Does anyone know of a good way to do this.

Regards
Scott Blood
Senior Developer
www.betfred.com

[Truong Hong Thi]

Hi Scott,

I guess you tried using Form.Show() instead and disabling the owner
form?

Thi
http://thith.blogspot.com

[Kevin Spencer]

Use Show instead of ShowDialog.

--
HTH,

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

The devil is in the yada yada yada
"scott blood" <sc*********@hotmail.comwrote in message
news:%2******************@TK2MSFTNGP03.phx.gbl...

Hello,

We currently have an application that has a lot of screens that allow
users to add new data to the system. These forms are currently accessed
via a browse form, such as the employee's browse form. The user would
access the Add Form by clicking on the Add Employee Button.

Unfortunatly when you use MyForm.ShowDialog(this), the entire application
is locked out, which is the default and accepted behaviour of Windows
Forms.

However, i need the ability to only disable access to the browse form that
has called the Add screen and ensure the rest of the application stays
responsive.

I have tried quite a few ways of doing this, but none of them are
effective enough. Does anyone know of a good way to do this.

Regards
Scott Blood
Senior Developer
www.betfred.com

[scott blood]

Guys.

Thanks for your repsonse it is much appreciated, however this is not a
suitable method for us because we need the form to act as though it is modal
only affecting the form that initiated it.

Simply using show and setting enabled to false of the calling form does not
produce the desired effect.
"Kevin Spencer" <sp**@uce.govwrote in message
news:%2******************@TK2MSFTNGP04.phx.gbl...

Use Show instead of ShowDialog.

--
HTH,

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

The devil is in the yada yada yada
"scott blood" <sc*********@hotmail.comwrote in message
news:%2******************@TK2MSFTNGP03.phx.gbl...

>Hello,

We currently have an application that has a lot of screens that allow
users to add new data to the system. These forms are currently accessed
via a browse form, such as the employee's browse form. The user would
access the Add Form by clicking on the Add Employee Button.

Unfortunatly when you use MyForm.ShowDialog(this), the entire application
is locked out, which is the default and accepted behaviour of Windows
Forms.

However, i need the ability to only disable access to the browse form
that has called the Add screen and ensure the rest of the application
stays responsive.

I have tried quite a few ways of doing this, but none of them are
effective enough. Does anyone know of a good way to do this.

Regards
Scott Blood
Senior Developer
www.betfred.com

[Peter Thornqvist]

Scott,

could you explain the difference between "we need the form to act as though
it is modal only affecting the form that initiated it" and "using show and
setting enabled to false of the calling form does not produce the desired
effect"?
--
Regards, Peter

[Richard]

Scott,

Thanks for your repsonse it is much appreciated, however this is not a
suitable method for us because we need the form to act as though it is modal
only affecting the form that initiated it.

Simply using show and setting enabled to false of the calling form does not
produce the desired effect.

Could you not fire up the new form in or from a new thread? Just
thinking on my feet here. I guess you could wrap it up into a function
or something.

Richard