Is there a global validate on a winform?

[jjbutera]

I know how to use the ErrorProvider in my winforms..or do I? I validate
the values and set the ErrorProvider in the validating event. If not
valid, I set e.Cancel = True. I clear the ErrorProvider in the
validated event.

Is there a way to know if all validated controls pass validation when
the user clicks an OK button? In ASP.Net there's the Page.IsValid
method. Is there something similar in winforms, or do I still have to
write an overall validate routine to fire on the button click? I tried
Me.Validate(), but that always returned true...I guess I have to put my
final validations in the forms validate event?

It seems to me that form validation is much easier in ASP.Net apps.

[Bruce Wood]

It does appear in msdn2's documentation for the ContainerContro l class.
The documentation doesn't say so, but it appears to have been added in
..NET 2.0, which is why neither you nor I can find it in our docs for
..NET 1.1 (aka VS 2003).

jj******@hotmai l.com wrote:

In what class is Validate and ValidateChildre n a member? In searching
the VS .Net 2003 help, there is no entry for ValidateChildre n. What am
I missing here?

Dave Sexton wrote:

Hi,

Hmmm, am I missing a thread,

Do you mean that you can't see our posts? What news reader are you using?

or is ValidateChildre n in 2.0 only?

Nope.

I went ahead and created a custom control that inherits Textbox and
added this simple method (sorry for the VB instead of c#):
>

<snip code>

>
This gives me what I want. I think I'll add a property called something
like AllowExitOnFail edValidation that I can check so I could still fire
Validating but choose whether or not to set e.Cancel. That way the
error will be shown, but they could still leave the field. Sometimes
users may want to tab past a required field to fill out another part of
form first. In my OK click, I do the following:
>

<snip code>

I think Bruce Wood's post addresses your concerns. Just set CausesValidatio n = false on your control too so that the user can tab
through it without being forced to enter valid data.

--
Dave Sexton

[Dave Sexton]

Hi Bruce,

Well that's just terrible. Thanks for the info and sorry for the confusion.

Hey, at least they addressed the issue in 2.0 :)

--
Dave Sexton

"Bruce Wood" <br*******@cana da.comwrote in message news:11******** *************@b 28g2000cwb.goog legroups.com...

It does appear in msdn2's documentation for the ContainerContro l class.
The documentation doesn't say so, but it appears to have been added in
.NET 2.0, which is why neither you nor I can find it in our docs for
.NET 1.1 (aka VS 2003).

jj******@hotmai l.com wrote:

>In what class is Validate and ValidateChildre n a member? In searching
the VS .Net 2003 help, there is no entry for ValidateChildre n. What am
I missing here?

Dave Sexton wrote:

Hi,

Hmmm, am I missing a thread,

Do you mean that you can't see our posts? What news reader are you using?

or is ValidateChildre n in 2.0 only?

Nope.

I went ahead and created a custom control that inherits Textbox and
added this simple method (sorry for the VB instead of c#):

<snip code>

This gives me what I want. I think I'll add a property called something
like AllowExitOnFail edValidation that I can check so I could still fire
Validating but choose whether or not to set e.Cancel. That way the
error will be shown, but they could still leave the field. Sometimes
users may want to tab past a required field to fill out another part of
form first. In my OK click, I do the following:

<snip code>

I think Bruce Wood's post addresses your concerns. Just set CausesValidatio n = false on your control too so that the user can
tab
through it without being forced to enter valid data.

--
Dave Sexton