text box is NOT showing full text

ilcaa72

Registered User.
Local time
Today, 14:55
Joined
Nov 27, 2016
Messages
38
i have a text box in a form that is connected to a table, the text box seems to cutoff the text once it reaches a certain length.

In my table the text column is it formatted as "long text". I did a Len() and the max length is 277 characters. I have Grow = YES and Shrink YES

I dont know what other options i should choose to show the entire text in the text box. let me know if everyone has ideas.. here is a screenshot.
 

Attachments

  • Acess_TxtBox Error.png
    Acess_TxtBox Error.png
    47.1 KB · Views: 670
Change the property "Text Format" to "Rich Text".
 
thanks for the reply. Minty, your link refers to using a Memo Type to open the box up to > 255 Chars. I am using 2016 and the "Long Text" is now considered the memo type.


i have made changes to both "Rich Text" on the table and on the TxtBox in the form. it still is cutting it off at 255 characters. Also it has a "date picker" but under format, it only give options for number, dates, etc...

here is another screenshot
 

Attachments

  • Access txtBox Error2.png
    Access txtBox Error2.png
    46.7 KB · Views: 477
Did you read the rest of the suggestions. They apply as memo and long text are one and the same. No idea why you would format it as general date. Delete that option.

What does your calculated field do?

Sent from my Nexus 7 using Tapatalk
 
i did not format as general date, Access for some reason has the weidiest default options, even when you choose data type as Text...

they are off and still maxs out at 255 char. my source is just a cell in a column of a table, no queries.. no combox box, just a textbox

here is another screenshot....
 

Attachments

  • Access_txtBox Error.png
    Access_txtBox Error.png
    56.8 KB · Views: 416
What is the RecordSource of the form? Some queries will not return a text field longer than 255 chars. I believe a UNION query, for instance, will not return a memo longer than 255 chars.
 
ControlSource should just be the name of the field in the RecordSource, not...
Code:
=[Question]
 
questions on what the proper procedure regarding adding "Source Control"...

If i use the "build" dialogue and select the table, then the record source it returns "=[Question]" your saying this is incorrect? is there ever a time you would use the "build button" ?

also... do I need to establish a "Record Source" in a Form BEFORE being able to add a "Source Control"

I have been experimenting and I am getting alot of "#Name?" but i havent figured out the logic.. a bit confusing...
 
In Access the fastest way to get data into a form is use the form's RecordSource property. Set this property to the name of a table or query, or to a SQL SELECT statement. Once that is done, the open form automatically creates and maintains its own recordset, and a form thus configured is said to be a "bound form."

To show data in controls using a bound form, set the ControlSource property of a given control to the name of a field exposed by the form's recordset.

When you use the "=" sign as the first character in a control's ControlSource property, you are indicating that the control will produce its value from an expression, not from a field in the form's recordset.

Hope this helps,
 
after extensive testing and searching, i came across those who had the same issues...

the issue stems from importing from Excel...

as per Microsoft, they scan the first 20 rows if a majority is short text they label "Short text" and import the first 255 char only. Though you can make the changes after import, it doesnt matter. The import was truncated..

the solution is... when using the import wizard make sure you label the data type for each row BEFORE importing... dont just assume you can change it, if its over 255 char it will be truncated unless you label as "Long Text" within the import wizard.

thanks for your help.
 

Users who are viewing this thread

Back
Top Bottom