Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6865811
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T03:06:01+00:00 2026-05-27T03:06:01+00:00

This is some old code that I am not too familiar with : RequiredFieldValidator

  • 0

This is some old code that I am not too familiar with :

 RequiredFieldValidator vldRequired = new RequiredFieldValidator();
                    vldRequired.Display = ValidatorDisplay.Dynamic;
                    vldRequired.Text = "*";
                    vldRequired.ControlToValidate = "txtSetting";
                    vldRequired.ID = "vldRequired";
                    vldRequired.Enabled = true;
                    vldRequired.ErrorMessage = SettingTitle + " is required";
                    returnCell.Controls.Add(vldRequired);

Where, IF you tab passed a required field the * will show up next to it. THE ErrorMessage only shows up when a Submit is clicked (that is all fine).

However, once you fill in the required field and tab out of the input, the “*” goes away but the ErrorMessage stays — I cannot figure out how to make that ErrorMessage go away when the * does.

Help?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T03:06:02+00:00Added an answer on May 27, 2026 at 3:06 am

    Ok, I just ran into a similar issue on one of my projects. It’s been a while since I’ve used the requiredFieldValidator. Try removing your Text Property as it interferes with the Error Message. Also ensure that you don’t have a Validation Summary on the page as that may cause fixed messages to linger in front of the user even though they have corrected the the problem on the client side.

    RequiredFieldValidator vldRequired = new RequiredFieldValidator();
                        vldRequired.Display = ValidatorDisplay.Dynamic;
                        //vldRequired.Text = "*";
                        vldRequired.ControlToValidate = "txtSetting";
                        vldRequired.ID = "vldRequired";
                        vldRequired.Enabled = true;
                        vldRequired.ErrorMessage = SettingTitle + " is required";
                        returnCell.Controls.Add(vldRequired);
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have some code kicking around that uses this old internal Sun package for
I just found this in some old code, and I'm not sure what it
I found this statement is some old code and it took me a second
This is some code I found on the internet. I'm not sure how it
this is some code that SDL requires in visual studios 2005 in order for
I'm encountering this error while compiling some old VC++ 6.0 source code. error C2632:
Case Quite often I find myself staring at some old code that doesn't look
I have some old Haskell code that includes QuickCheck test cases. Newer versions of
I am working on editing some old C++ code that uses global arrays defined
Recently, we discovered odd behavior in some old code. This code has worked for

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.