By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,214 Members | 2,066 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,214 IT Pros & Developers. It's quick & easy.

Custom validation control question.

P: n/a
Hi:

I'm not sure how to control the following behavior..
Sequence of events [1-3] are working properly #4 is the problem:

1] User enters invalid data in a textbox and click submit
2] Server side validation runs, and the page is redisplayed the
CustomValidator.ErrorMessage is displayed because validation failed.
3] The user then corrects the data and resubmitts the page successfully and
the page redirects to a new page.

everything is ok so far, but if

4] the user then clicks the Back button on their browser, when the first
page is redisplayed, CustomValidator.ErrorMessage is visible on the first
page even though the data has been corrected.

Any ideas appreciated,

Thanks
peter
Jun 8 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
the best approach is to add a client validation routine, so there is no
postback. you can expire the page, but then the back button will give
the repost data message.

-- bruce (sqlwork.com)

peter wrote:
Hi:

I'm not sure how to control the following behavior..
Sequence of events [1-3] are working properly #4 is the problem:

1] User enters invalid data in a textbox and click submit
2] Server side validation runs, and the page is redisplayed the
CustomValidator.ErrorMessage is displayed because validation failed.
3] The user then corrects the data and resubmitts the page successfully and
the page redirects to a new page.

everything is ok so far, but if

4] the user then clicks the Back button on their browser, when the first
page is redisplayed, CustomValidator.ErrorMessage is visible on the first
page even though the data has been corrected.

Any ideas appreciated,

Thanks
peter

Jun 8 '07 #2

P: n/a
Hi Peter,

As Bruce has suggested, one way to prevent this behavior is disable client
output cache in your page , thus whenever you click back button at client
browwer after a postback, it should display the expired page screen.

Also, another means you can consider is manually use Response.Redirect to
relocate the page to the current location. e.g.

============
#postback handler
{
//after finishing work

Response.Redirect(the page want to display);
}
=============

Also, this can help prevent resubmit the page when user click refresh
button.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Jun 11 '07 #3

P: n/a
Hi Peter,

Have you got any progress on this issue or does the suggestion in previous
messages help some? If there is anything else we can help, please feel free
to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Jun 13 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.