Interesting, I've never heard that before.
I know Validate gets called automatically sometime after Page_Load. But if
you want to use IsValid in Page_Load I thougth you had to precedeed with a
Validate.
From docs:
"Note If you want to perform this check during Page_Load, you must
manually call the Validate method first."
http://msdn.microsoft.com/library/de...mmatically.asp
Greg
"bruce barker" <> wrote in message
news:%...
> IsValid calls Validate() if it has not been called.
>
> -- bruce (sqlwork.com)
>
>
> "Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
> news:...
> > Page.Validate is not the same as Page.IsValid (obviously)
> >
> > I've never found a reason to call Page.Validate myself (not that there
> > probably aren't some good ones). Here is a contrived example from the
> help
> > files.
> >
> > Sub Page_Load
> > If Not IsPostBack
> > ' Validate initially to force the asterisks
> > ' to appear before the first roundtrip.
> > Validate()
> > End If
> > End Sub
> >
> > I always do a check of Page.IsValid first thing in my button click
events.
> >
> > If Not Page.IsValid Then Return
> >
> > Like Bruce said, if (for whatever reason) your client-side javascript
> didn't
> > prevent the page from posting in the first place then the server
validate
> > events will run. You use Page.IsValid to make sure that the server
> > validation didn't catch anything.
> >
> > HTH,
> > Greg
> >
> >
> > "bruce barker" <> wrote in message
> > news:%...
> > > if the browser is not ie, or javascript is disabled, all validation is
> > > serverside. for serverside validation to run you must call
Page.Validate
> > or
> > > Page.IsValid.
> > >
> > > -- bruce (sqlwork.com)
> > >
> > >
> > > "Jim Heavey" <> wrote in message
> > > news:22D55F42-5B1E-4DDB-94C8-...
> > > > When should you use the Page.Validate() method? I thought you would
> use
> > > this method if you have some Server side validation (CustomControl's)
> you
> > > wanted to use and this would cause them to be invoked. I am probably
> > wrong
> > > about that.
> > > >
> > > > If I am suppose to use this function, the edits seemed to be invoked
> > even
> > > when you have pressed the cancel and the "CausesValidation" is set to
> > false.
> > > Is there a way to get around this (might just be an acedemic question
if
> I
> > > should not be running Page.Validate() if the first place.
> > > >
> > > > Thanks in advance for your assistance!!
> > >
> > >
> >
> >
>
>
