My product, "Professional Validation And More" at
http://www.peterblum.com/vam/home.aspx, is a replacement for Microsoft's
validators. It includes "validation groups". Validation groups lets you
assign a group name to a button and the validators it fires. Professional
Validation And More is designed to overcome the numerous limitations of
Microsoft's validators. I've put together a list of the limitations at
http://www.peterblum.com/vam/valmain.aspx. Of the 19 limitations, only two
are solved in next year's ASP.NET 2.0: validation groups and setting focus
to the field with the error.
--- Peter Blum
www.PeterBlum.com
Email:
PLBlum@PeterBlum.com
Creator of "Professional Validation And More" at
http://www.peterblum.com/vam/home.aspx
"Raterus" <raterus@spam.org> wrote in message
news:OPnlZ7YTEHA.1472@TK2MSFTNGP12.phx.gbl...
If a button doesn't need to trigger validation, you can always set the
causesvalidation property to false. From what I've read, there will be
Validation Groups in ASP.NET 2.0
"TJS" <nospam@here.com> wrote in message
news:eUM2iUYTEHA.1508@TK2MSFTNGP11.phx.gbl...[color=blue]
> by multiple forms I mean they are all visible all the time. such as a
> search form and a logon form etc.
>
> the problem seems to be with the validation. The page wants to validate[/color]
all[color=blue]
> forms and therefore prevents any form from being submitted.
>
> I didn't want to have to write validation in the onclick events area. I[/color]
was[color=blue]
> hoping to keep it in the template area.
>
>
> "Lerp" <admin@officience.ca> wrote in message
> news:%23sdgXBYTEHA.1244@TK2MSFTNGP10.phx.gbl...[color=green]
> > Hi there,
> >
> > Use one big form and sepearate the sections using panels is one way of
> > getting over that. You can toggle the visible property of the panel[/color][/color]
(part[color=blue][color=green]
> > of fomr in question) when needed by setting its visible property to[/color][/color]
true.[color=blue][color=green]
> >
> >
> > Cheers, Lerp :)
> >
> >
> >
> > Here's an example:
> >
> >
> > Sub ChangePanelVisibility(Sender As Object, E As EventArgs)
> >
> > If Sender.Text = "Show Panel One" Then
> > myFirstPanel.visible = true ' SET TO TRUE HERE
> > mySecondPanel.visible = false
> > myThirdPanel.visible = false
> > myFourthPanel.visible = false
> > End If
> >
> > End Sub
> >
> >
> >
> > <form ID="myForm" runat="server">
> >
> > <asp:panel ID="myFirstPanel" CssClass="myCssClass" runat="server">
> > First section of form
> > </asp:panel>
> >
> > <asp:panel ID="mySecondPanel" CssClass="myCssClass" runat="server">
> > Second section of form
> > </asp:panel>
> >
> > <asp:panel ID="myThirdPanel" CssClass="myCssClass" runat="server">
> > Third section of form
> > </asp:panel>
> >
> > <asp:panel ID="myFourthPanel" CssClass="myCssClass" runat="server">
> > Fourth section of form
> > </asp:panel>
> >
> >
> >
> > <asp:Button id="ShowPanelOneButton" text="Show Panel One"
> > OnClick="ChangePanelVisibility" runat="server" CssClass="but" />
> > <asp:Button id="ShowPaneltwoButton" text="Show Panel Two"
> > OnClick="ChangePanelVisibility" runat="server" CssClass="but" />
> > etc...one button for each panel if you wish here...
> > </form>
> >
> >
> >
> >
> > "TJS" <nospam@here.com> wrote in message
> > news:OqQwm8XTEHA.564@TK2MSFTNGP11.phx.gbl...[color=darkred]
> > > what are folks doing to get around limitation of one server form per[/color][/color]
> page[color=green]
> > ?[color=darkred]
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]
