Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Text fields

  Asked By: Bob    Date: Oct 26    Category: Sharepoint    Views: 12955

I'm a little dissapointed that the limit for text fields in lists seems to
be 255. Am I missing something?

Share: 

 

15 Answers Found

 
Answer #1    Answered By: Alisha Holmes     Answered On: Oct 26

255 is the limit  for a text  unless you go for a multiline field. Its all
got to do with how the data is stored in the database. Text fields  are
nvarchar columns of 255 chars in the database.

 
Answer #2    Answered By: Damon Garner     Answered On: Oct 26

I believe text  areas (multiple lines of text) support up to two GB of
text. You can always set the "Number of Lines to Display:" to 1 if you
want it to render like a single line text box with a tiny scroll bar on
the end.

 
Answer #3    Answered By: Percy Beach     Answered On: Oct 26

I swear I tried that and multiple lines of text  were still limted to 256
characters. At least on my server. I'll try again, thanks.

 
Answer #4    Answered By: Mary Adams     Answered On: Oct 26

OK, I just tried it. Made a document library. Added a field of type
multiline, made the number of lines 22. Added a document, when I put in
text > 255 characters it rejected it stating that 255 was the limit  for text
fields. Note: this is in a WSS site, would that make a difference??

So, if the limit is larger than 255, what configuration may be screwed up on
my system perhaps that is disallowing me to use one?

 
Answer #5    Answered By: Laura Walker     Answered On: Oct 26

I, too, am facing the dreaded 255 character limit. I have not found a way around it, but it would certainly be useful to be able to put more characters in there. I have a specific situation where we record notes about a document as it passes through a process--sometimes takes a couple of weeks worth of meetings to get it done. Those notes could often use more than 255 characters.

Is this just a setting somewhere? I could not find it.

 
Answer #6    Answered By: Kalyan Pujari     Answered On: Oct 26

I misunderstood your initial question. text  fields in "Document
Libraries" ARE limited, text fields  in "Lists" are NOT limited. I don't
recall why but I know who will. I'll ping her and get back to you. But
you are correct, text fields are limited on a Document Library.

I faintly remember something about the technology used to interface the
fields to/from Office (Word/Excel/etc.) properties being limited so the
WSS library had to be limited too.

 
Answer #7    Answered By: Katy Patton     Answered On: Oct 26

Yes, it did work correctly on a list. Also, on a list, multiline fields
have a radio button to allow for rich text  but on a document library field
there is no radio button.

I guess I could do a list and allow attachments for the document, but I'd
like the features of a document library.

I have been thinking about schema.xml modifications, but obviously I'd like
to avoid that for such a simple thing.

 
Answer #8    Answered By: Ana Payne     Answered On: Oct 26

I'm certain that it's not just a setting somewhere. It's a technical
limitation. More when I get the details.

 
Answer #9    Answered By: Christop Mcfadden     Answered On: Oct 26

It’s a limitation between the transfer from a doclib to the properties in Office documents. text  fields are limited to 255 characters in Office and everything has to be converted to a text field (for example even though you can create a choice field as an Office property it doesn’t map to a choice field in a SharePoint doclib). While on the other hand, SharePoint lists  are only limited by SQL and the schema for lists in SharePoint itself so do not have the same issues. As far as I can find in my wanderings, there’s nothing you can do configuration wise (SCHEMA.XML) to change this (and don’t even begin to think about changing the basetypes in the config files to dance around this or else face a whole new Pandora’s box. That’s just as bad as people wanting to write directly to the database).

 
Answer #10    Answered By: Lacey Daniels     Answered On: Oct 26

Could this have something to do with the fact that the doclib attributes are also stored in the word doc itself?

 
Answer #11    Answered By: Megan Martin     Answered On: Oct 26

OLE property stream

That's the technical reason (thanks Jill) for the limitation I was
grasping at this morning.

You can read more about it here (thanks Mike, Gabe, and Zlatar):
wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=32

 
Answer #12    Answered By: Donta Kirkland     Answered On: Oct 26

OK well that sucks. I mean they could have just as well truncated the field
on output/input.

So if my choices are a custom list vs. a document library with a field that
will sometimes get longer than 255 charaters, what should I do?

The options I see are a) a doc library with a field that I sometimes
abbreviate; or b) a custom list with the larger field and place the pdf
files in an attachment to the list item.

General requirements:
1) Documents are static, so revisions are not important.
2) Search is important of both the field that would have 255 (or more)
characters and the documents (normally pdf files).
3) Security is not that important.

So are documents attached to a list item included in search?

 
Answer #13    Answered By: Cade Velazquez     Answered On: Oct 26

I'm not an expert on search. But, I don't believe that List item
attachments are included in search.

 
Answer #14    Answered By: Ariana Christensen     Answered On: Oct 26

I encountered the same problem.
I do have a "multiple lines of text" field as property in my WSS
document library.
The editform does not accept moet than 255 characters.
If I add a value of say 1000 characters to the ntext? Field in the
database, no problem. (It is a ntext field)
When opening the editform.aspx, it will show me the 1000 characters.
After changing some (other) value and click [save] the forms comes with
the no more than 255 char warning


Any ideas how to change the validation of the fields  or something else
to fix this.

 
Answer #15    Answered By: Mauri Premathilake     Answered On: Aug 10

Brianok: Try LONG PATH TOOL!!! It'll be the best solution.For LONGER FILE NAMES,PATHS,FOLDERS it is the best.

 
Didn't find what you were looking for? Find more on Text fields Or get search suggestion and latest updates.




Tagged: