Text data type size

[aman]

Hi All

I have few textboxes in a form that has Text data type and sixe limit is set to max 255 characters. But my problem is the users need to enter sometimes more than 255 characters and in that case they receive error messages.

I know we can use Memo data type but my manager said it has some disadvantages so not sure what do we need to do?

ANy help will be much appreciated.

Thanks

 

[Tieval]

The only real disadvantage is not being able to sort memo fields properly.

Only other way is to use more than field in a table and join them as a string in a textbox on a form, personally I think this is hard work.

 

[so10070]

I work with Access 2013 and text fields are divided in two kind of text fields: a short and a long text field. The long text field is the replacement of the memo field. I use this kind of field in several forms/reports without any problem. Why else would this kind of data type developed in Access.

 

[The_Doc_Man]

To answer the original question, a MEMO field in older versions of Access cannot support being an index, can't be part of a relationship, and can't easily be searched from a query.

In my current project, I have not had to use the LONG TEXT type so have to defer any questions to the other forum members.

 

[so10070]

Why indexing a memofield or set a relationele on it. Then I think there's a problem with the normalization. Use it as a pseudo word processor: a field to put in some text more than 250 characters. But remember: Access is no word processor!

 

[missinglinq]

One of the Cardinal rules to having a well designed, normalized database is that no single field will contain more than one individual piece of data. Data stored in Memo fields should be restricted to "notes" or narrative type information, such as a salesman's notes on a customers, a doctor's progress notes on patients, or, as in your case, client notes.

Working primarily in a Heath Care environment, I've used Memo fields extensively for a number of years, without ever having problems, corruption or otherwise. I've always attributed this to the fact that I've followed one simple rule:

Never, never, never place data in a Memo field if there any possibility that you will ever need to search, sort, parse or in any other way manipulate the data!

Because many Queries perform some of these functions, you have to take care in using them in Queries or they will likely be truncated to 255 characters.

Allen Browne has some excellent advice explaining how to deal with Memo Fields and Queries:

Microsoft Access tips: Truncation of Memo fields

Linq ;0)>