Text box with more than 255 characters

[ssissons]

I apologize if this is a duplicate question.



In Access 2007 -

I have a form with a text box. I have a memo field in multiple tables. I can type more than 255 characters in the text box, save it to the memo field. If I look at the table in datasheet format, the entire contents of the textbox (> 255) are saved. BUT, going back to the form, if I retrieve the memo field and put the contents into the text box, it is cut off at the 255 character point. Is there a way to change the limit on the text box besides binding it to a table field, or is there another control which will allow for more than 255 characters?

Thanks!
Scott

[John_G]

Sounds like there may be an issue with how you are populating the text box when you retrieve the memo field.

How are you doing that, if the text box is not bound to the table field?

John

[Missinglinq]

John's got the right idea...basically Queries truncate Memo Fields to 255 characters, as do some formatting functions. Allen Browne has an excellent article on the subject here:

http://allenbrowne.com/ser-63.html

Linq ;0)>

[ssissons]

Here is the relevant code. LongDescription is defined as a MEMO field in the table. txtDescription is the text box, allowing for multi-line entry.

strSelect = "SELECT DISTINCT Requestor, Create_Date, Status, ShortDescription, LongDescription, Priority, System, AssignedTo FROM Issues WHERE TTP_No = " & varSelectedTTP
Set rstIssues = CurrentDb.OpenRecordset(strSelect)

If varSelectedTTP > 0 Then
If rstIssues.RecordCount = 0 Then
MsgBox "That TTP number does not exist in the database."
ResetTTP
Else
With rstIssues
txtTTP_No = CStr(varSelectedTTP)
txtRequestor = !Requestor
txtCreateDate = !Create_Date
cboStatus.Value = !Status
txtShortDescription = !ShortDescription
txtLongDescription = !LongDescription
cboPriority.Value = !Priority
cboSystem.Value = !System
txtAssignedTo = !AssignedTo
txtCreateDate.Visible = True
lblCreateDate.Visible = True
End With

[Missinglinq]

You're using SELECT DISTINCT in your SQL Statement; go back to Allen Browne's article and read the entry under Uniqueness and it should be apparent what the problem is.

Linq ;0)>

[ssissons]

That was it! Removing the DISTINCT solved the problem. Thanks so much!

[Missinglinq]

It's all in the details!

Good luck with your project!

Linq ;0)>