Wrox Programmer Forums
|
BOOK: ASP.NET 3.5 Website Programming Problem Design Solution
This is the forum to discuss the Wrox book ASP.NET 3.5 Website Programming Problem Design Solution by Chris Love; ISBN: 978-0-470-18758-6
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: ASP.NET 3.5 Website Programming Problem Design Solution section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old February 4th, 2010, 01:41 PM
Registered User
 
Join Date: Jan 2010
Posts: 8
Thanks: 0
Thanked 1 Time in 1 Post
Default Required field validators and tab panels--bug?

This might be of interest to people trying to make the C# version work. On the AddEditUser page there is an Ajax tab container and tab panels.
On the first tab panel there are several Required field validators tied to textboxes for updating user information. On the second tab there is a
Button for updating Roles checked off on the same tab.
Now this button will simply not work i.e. clicking the button doesn't trigger the onclick event to update roles. What I found out was that if some
fields are not filled in on the first tab this is the reason that the button on the second tab will not work. So it seems that if you have field validators
on a tab this will effect buttons on other tabs. You cannot see the required field warnings when you are on another tab than where the field validators
are. Clicking on buttons on other tabs will simply not work when the fields on other tabs are blank. A work around is to have the fields validated in the
"update" link (and it's onclick event) on the first tab rather than have required field validators.
 
Old February 4th, 2010, 02:55 PM
Registered User
 
Join Date: Jan 2010
Posts: 8
Thanks: 0
Thanked 1 Time in 1 Post
Default a better workaround

A better workaround is to use Validation groups. Please see

http://www.dotnet-guide.com/validationgroups.html





Similar Threads
Thread Thread Starter Forum Replies Last Post
[Resolved] Use of Required Field Validators snufse ASP.NET 2.0 Basics 5 March 11th, 2008 09:53 AM
Enabling and disabling Required field Validators mrufus General .NET 0 June 27th, 2006 03:44 AM
Required Field Validator RGB ASP.NET 1.0 and 1.1 Basics 3 March 31st, 2006 03:31 PM
Required field dependent on another field... nkrukovsky Access VBA 3 January 14th, 2004 10:37 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.