RangeValidator error displays and disappears quickly with textbox format

Question

1.00/5 (1 vote)

See more:

I have a web form that displays different error messages. I am using the Range Validator for displaying the error message. When a user enters in a number the error message displays very quickly. I changed my properties to EnableClientScript= true Display= Dynamic and get the same issue. The textbox is formatted with a code to add commas where needed. Here is the code behind:

C#

TextBoxFTUG.Text = string.Format("{0:0,0}", double.Parse(TextBoxFTUG.Text));

Here are the properties for the textbox:

ASP.NET

<asp:TextBox ID="TextBoxFTUG" runat="server" Width="180px" AutoPostBack="True" 
                    ontextchanged="TextBoxFTUG_TextChanged">0</asp:TextBox>

The AutoPost Back is there to change the data to the format when the user clicks or tabs to the next textbox.

I also have a code behind that does calculations for the RangeValidator.

C#

double txtVal6 = Convert.ToDouble(TextBoxLYFTUG.Text);
        double minVal6 = (txtVal * 0.8);
        double maxVal6 = (txtVal * 1.2);
        RangeValidatorLYFTUG.MinimumValue = minVal6.ToString();
        RangeValidatorLYFTUG.MaximumValue = maxVal6.ToString();

When the user clicks on the submit button all of the errors display that should have displayed earlier. How can I get the error to display when the user enters data that is 20% higher/lower in the textbox?

Posted 10-Oct-14 4:27am

Computer Wiz99

Updated 13-Oct-14 5:11am

v4

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

hypermellow · Answer 1 · 2014-10-10T04:36:00

Solution 1

Hi,

Have you had a look at the Validation Summary control?

[edit]
It will also help the validation appear more fluid if you add the following properties to your validator controls:

HTML

EnableClientScript="true"
Display="Dynamic"

[/edit]

Hope it helps.

Posted 10-Oct-14 4:36am

hypermellow

Updated 10-Oct-14 4:39am

v2

Comments

Computer Wiz99 10-Oct-14 10:48am

Thanks hypermellow. Will this also reset the error message when the user changes the number? EX: If the user enters 12,345 and the error displays and the user should have entered 123,456. Will the error go away?

hypermellow 10-Oct-14 11:00am

Yup, it should do - as setting EnableClientScript to true should perform the initial validation in the browser (without a postback) via client script.
... also, it's worth noting that even though the validation is performed client side, it is important to confirm the validation was successful on the server too by checking Page.IsValid() in your code behind.

Computer Wiz99 10-Oct-14 11:39am

Where would I put Page.IsValid() in code behind? I did change the properties to the validation but is still not working.

hypermellow 13-Oct-14 5:37am

I see you've changed your question now, what do you mean the validation is still not working?
The check for Page.IsValid() should go in the event handler for the submit button click.

Computer Wiz99 13-Oct-14 5:51am

When the user enters their data and tab to the next textbox it should fire. This needs to happen without clicking the submit button. It was working before I formatted the textbox.

hypermellow 13-Oct-14 6:07am

OK, I'm confused ... why do you have the autopostback attribute set to true, and an ontextchanged event defined on some of your textboxes?
If you have EnableClientScript=True and Display=Dynamic then the validation will happen immediately without a postback.

Computer Wiz99 13-Oct-14 6:09am

Some of tge textboxes do calculations. The first two textboxes don't.

hypermellow 13-Oct-14 6:23am

The auto postback/textchanged postback is probably not the best choice of design, a javascript call to a webservice that performs the calculation would have been a better choice. That way you won't be mixing client and server side validation elements.

Does the postback still happen when user tabs out of the textbox? ... if so, can tell the clientscript to revalidate using Page_ClientValidate() and then checking Page_IsValid.
http://www.codeproject.com/Articles/426761/Exploring-ASP-NET-Validation-Controls

Computer Wiz99 13-Oct-14 6:32am

I see what you are saying but can't make changes like that right now. I think the format of the textbox is what threw it off. How can I get tge validator to except commas?

hypermellow 13-Oct-14 6:48am

You should be able to switch from the RangeValidator control to a CompareValidator ... just remember to set the type to Currency, and operator to DataTypeCheck.

Perhaps something like:
<asp:CompareValidator ID="cvLYFTUG" runat="server" ControlToValidate="TextBoxFTUG" Type="Currency" Display="Dynamic" Operator="DataTypeCheck" ErrorMessage="Not a valid format" />

Computer Wiz99 13-Oct-14 8:54am

I don't think I would need the CompareValidator. I am not comparing anything. The validator should fire if the value is 20% higher/lower.

Ex.

Textbox1 has a value of 100 and the user enters 121 in textbox2. The validator should fire because the value in textbox2 is 20% higher then the value in textbox1.

hypermellow 13-Oct-14 8:59am

I suggested the CompareValidator as you asked how to allow commas in the user input. The CompareValidator can be used to check the input is of the correct type (i.e.- currency).
... you could then use an additional CompareValidator to check the value is within an allowed range - or a CustomValidator would work here too.

Computer Wiz99 13-Oct-14 9:00am

Okay. How would the Custom Validator work in this? I never used it.

hypermellow 13-Oct-14 9:08am

CustomValidator allow you to use a boolean function that you create to perform the actual validation.

http://msdn.microsoft.com/en-us/library/f5db6z8k%28v=vs.90%29.aspx

Computer Wiz99 13-Oct-14 9:25am

Thanks. Can you explain to me why did the range validator stop working when I formatted the textbox with the string code?

hypermellow 13-Oct-14 9:30am

Hi, the RangeValidator stopped working as you specified its type attribute as an integer.
Have you tried the CustomValidator yet? ... if so, how are you getting on with it?

Computer Wiz99 13-Oct-14 9:48am

I have tried it but with no luck on my part. Maybe I am doing something wrong.

hypermellow 13-Oct-14 10:02am

... it should go something like this:

<asp:CustomValidator
id="cvValidate"
runat="server"
OnServerValidate="ValidationFunction"
...
...
/>
and in your code behind:
protected void ValidationFunction(object source, ServerValidateEventArgs args){
if(IsValidCondition(args.Value)==true){
args.IsValid =true;
}else{
args.IsValid =false;
}
}

public bool IsValidCondition(string sUserInput){
bool bOut=false;
...
...
validate user input
...
...
return bOUt;
}

Computer Wiz99 13-Oct-14 10:09am

Thanks for the code. I was looking at something when you asked me about the Autopostback. I have the autopostback for the first two textboxes because of the format. When the user enters 2000 and tabs to the next textbox it would change to 2,000. I have a code behind that does the calculations for the rangevalidator to see if the values are 20% higher/lower from the original value. When I removed the autopostback the validator worked but the format stopped working.

Computer Wiz99 13-Oct-14 10:45am

This is the code I have behind for the RangeValidator:

double txtVal6 = Convert.ToDouble(TextBoxLYFTUG.Text);
double minVal6 = (txtVal * 0.8);
double maxVal6 = (txtVal * 1.2);
RangeValidatorLYFTUG.MinimumValue = minVal6.ToString();
RangeValidatorLYFTUG.MaximumValue = maxVal6.ToString();