Skip to main content

Max Length not working for Multi Line Text Box : Solution

In almost all the web projects, we require a multiline TextBox control. It was annoying to find that maxLength property doesn't work on multiline textboxes. There is a workaround to accomplish this using RegularExpressionValidator. Following is the markup that will restrict the text box to maximum of 500 characters.



1
2
3
4
<asp:textbox height="100px" id="txtComments" maxlength="10" runat="server" textmode="MultiLine" width="320px"></asp:textbox>
 
 <asp:regularexpressionvalidator controltovalidate="txtComments" errormessage="Maximum 500 characters are allowed in comments box." id="regComments" runat="server" text="Maximum 500 characters are allowed in comments
box." validationexpression="^[\s\S]{0,500}$"> </asp:regularexpressionvalidator>




OR You it can be done so easily using javascript functions.



I suggest that we should put a javascript validator function so that user will not be able to enter characters more than the length specified, even cant paste any text with more than specified characters. Here are those javascript functions.



TextBox Control
1
2
<asp:textbox height="168px" id="txtBox" maxlength="2000" onbeforepaste="doBeforePaste(this);" onkeypress="doKeypress(this);" onpaste="doPaste(this);" runat="server" textmode="MultiLine" width="223px">                                                                                                                                       
                                                                                                                                  </asp:textbox>




Javascript:



1
2
3
4
5
6
7
8
9
10
// Keep user from entering more than maxLength characters
 
function doKeypress(control){
    maxLength = control.attributes["maxLength"].value;
    value = control.value;
     if(maxLength && value.length > maxLength-1){
          event.returnValue = false;
          maxLength = parseInt(maxLength);
     }
}




1
2
3
4
5
6
7
8
9
// Cancel default behavior
 
function doBeforePaste(control){
    maxLength = control.attributes["maxLength"].value;
     if(maxLength)
     {
          event.returnValue = false;
     }
}




1
2
3
4
5
6
7
8
9
10
11
12
13
14
// Cancel default behavior and create a new paste routine
 
function doPaste(control){
    maxLength = control.attributes["maxLength"].value;
    value = control.value;
     if(maxLength){
          event.returnValue = false;
          maxLength = parseInt(maxLength);
          var oTR = control.document.selection.createRange();
          var iInsertLength = maxLength - value.length + oTR.text.length;
          var sData = window.clipboardData.getData("Text").substr(0,iInsertLength);
          oTR.text = sData;
     }
}



One additional thing you have to do is to add maxLength property of text box on Server side Page Load.



1
2
3
4
5
protected void Page_Load(object sender, EventArgs e)
    {
txtBox.Attributes.Add("maxLength", txtBox.MaxLength.ToString());
            
}



Hope this will help you.


The Girl Who Played with FireI Love The WayPride Professional Pro Length Max 4" Golf Tees WhiteLaugh With Max Linder

Comments

Post a Comment

Popular posts from this blog

Call User-defined Function on Linked Server :SQL Server

If you try to invoke a user-defined function (UDF) through a linked server in SQL Server by using a "four-part naming" convention (server.database.dbo.Function), you may receive error message.  The reason is User-defined function calls inside a four-part linked server query are not supported in SQL Server. Thats why error message indicates that the syntax of a Transact-SQL statement is incorrect.  To work around this problem, use the Openquery function instead of the four-part naming convention. For example, instead of the following query Select * from Linked_Server.database.dbo.Function(10) run a query with the Openquery function: Select * from Openquery(Linked_Server,'select database.dbo.Function(10)') If the user-defined function takes variable or scalar parameters, you can use the sp_executesql stored procedure to avoid this behavior.  For example: exec Linked_Server.database.dbo.sp_executesql N'SELECT database.dbo.Function(@input)',N'@input...

Microsoft SQL Server 2005 Service Pack 3 for Windows 7 (64 bit)

You can download from here Microsoft SQL Server 2005 Service Pack 3 Overview Service Pack 3 for Microsoft SQL Server 2005 is now available. SQL Server 2005 service packs are cumulative, and this service pack upgrades all service levels of SQL Server 2005 to SP3. You can use these packages to upgrade any of the following SQL Server 2005 editions: Enterprise Enterprise Evaluation Developer Standard Workgroup Download Size: 326.0 MB http://www.microsoft.com/downloads/details.aspx?FamilyID=ae7387c3-348c-4faa-8ae5-949fdfbe59c4&displaylang=en Microsoft SQL Server Management Studio Express Service Pack 3 Overview Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical management tool for managing SQL Server 2005 Express Edition and SQL Server 2005 Express Edition with Advanced Services. SSMSE can also manage instances of the SQL Server Database Engine created by any edition of SQL Server 2005. Note: SSMSE cannot manage SQL Server Analysis ...

RDLC Report - Add column to a dataset in existing report and save report in older format ( 2008)

I have an rdlc that has a separately-defined dataset. The time has come that I have the need to add a column to one of the tables, which I can do without issue. However, when I open the rdlc to use the new column, it does not appear in the Report Data pane. This issue was reported to Microsoft here, but it was closed as by design. The workaround offered with the issue does not seem to work for VS2010 (refresh the dataset or the table; neither does anything). Solution The only way to add a column to a dataset that is already attached to an rdlc is to hand-edit the xml (i.e. open the rdlc with your favorite text editor and add a Field to the appropriate table). After doing this, the field appears in the Report Data pane in the Design Pane, and you can use it as if it were there from the beginning. Save the report. Replace Report tag with the following line Then remove the following head, //keep the data here ...