"Validation Groups" is the correct approach because it allows client-side
validation of a group of controls. In your case, those will be controls on a
single tab page.
Since ASP.NET 2.0 is not available yet, you cannot use this feature without
some clever hacks.
I wrote a replacement to Microsoft's validators that addresses its numerous
limitations and greatly expands validation. "Professional Validation And
More" (
http://www.peterblum.com/vam/home.aspx) includes validation groups
today. It also has 22 validators and they provide client-side validation on
many more browsers than just IE and IE/Mac that your current validators use.
It includes a utility to quickly migrate a page to my validators.
Here's how you would solve this with Professional Validation And More:
1. Convert the page using the utility
2. On each page, assign a name to the Group property of each validator. The
name should be the same across one tab page.
3. If you have a submit button on each tab page, set its Group property to
match.
4. If you have a submit button outside of the tabbed section, assign
Group="*" so it validates all pages.
5. In your onSelectedIndexChange event, call my function
VAM_ValidateGroup("[groupname]", true). It will return true if validation
succeeds. Always validate the group associated with the tabbed page.
--- Peter Blum
www.PeterBlum.com
Email:
PL****@PeterBlum.com
Creator of "Professional Validation And More" at
http://www.peterblum.com/vam/home.aspx
"Sam Sam" <ta*************@yahoo.com> wrote in message
news:uI**************@TK2MSFTNGP10.phx.gbl...
Thanx for your help.
but i am still not clear how can i prevent a user from naviagting to
next page without saving data on current page.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
