Mafunzalo
asked on
Linking a memo datatype to a textbox in a report truncates data at 255.
I have tried to apply the solution from " Solution Title: Report Text Box - HURRY!" but it doesn't work for me, for some reason. Tha data still truncates at 255 characters. Please try to keep your answer simple. I don't know VBA.
Mafunzalo
Mafunzalo
>> Try doing a "dummy" rpt
Using the rpt wizzard
Using the rpt wizzard
ASKER
I tried using the report wizard and design view. neither worked.
In design view, the fiels in question was the only field in the report.
In both attempts, Can Grow and Can Shrink were Yes.
I must be missing something.
In design view, the fiels in question was the only field in the report.
In both attempts, Can Grow and Can Shrink were Yes.
I must be missing something.
ASKER
BTW, I didn't get the dummy reports to work, so I didn't copy&paste into the real report...
delete the control from the report, select field list from the view menu and drag the memo field name onto the report. Access can get goofed up if you add an empty textbox and then change the datasource to memo or if you copy an existing textbox bound toa text field and then change the control source to a memo field.
Steve
Steve
ASKER
I created a report using Design View (totally empty)
I clicked Record Souce in the Properties box to get the query I'm interested in. The Field List populated.
I dragged and dropped the memo field from the Field List,
Went back to Properties and selected Yes for "Can Grow" and "Can Shirnk"
Hit View and the fields are still limited to 255.
I clicked Record Souce in the Properties box to get the query I'm interested in. The Field List populated.
I dragged and dropped the memo field from the Field List,
Went back to Properties and selected Yes for "Can Grow" and "Can Shirnk"
Hit View and the fields are still limited to 255.
ASKER
Whoa. New information.
The datatype of the field of the table that the query is working on is Memo and has more than 255 characters. OK.
When I run the report that includes the query, the data is limited to 255 characters.
When I run the query alone, the character-length of the data that is pulled from the table is limited to 255 characters. The table that is created from the query has the limitation, not the report. NOW what?
The datatype of the field of the table that the query is working on is Memo and has more than 255 characters. OK.
When I run the report that includes the query, the data is limited to 255 characters.
When I run the query alone, the character-length of the data that is pulled from the table is limited to 255 characters. The table that is created from the query has the limitation, not the report. NOW what?
ASKER
Another update that supoports the "Whoa." update.
When I do a report wizard and NOT use the query, the fields are not truncated!
But I have some relationships in the query that I need to keep (and don't know how to create in the Report Wizard, if it's possible). How can I reference the query in the report but keep the complete memo fields printing?
When I do a report wizard and NOT use the query, the fields are not truncated!
But I have some relationships in the query that I need to keep (and don't know how to create in the Report Wizard, if it's possible). How can I reference the query in the report but keep the complete memo fields printing?
ASKER
I increased the points to 300. I gotta get an answer!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks. I'll give it a try tomorrow.
ASKER
Computers are really strange.
My query is fairly complex and in order to try your solution, I started removing tables I could live without. I wpuld remove a table and then test it. Still bad. Remove. Test. Bad. Until there was just the main table where the majority of the data lived. Then I got the error, "The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data." [OK] [Help] OK closes it, Helpbrings up a blank screen. This is a select query. I removed the remaining fields until there was one: the memo field. I still get the "field is too small" error. Compact and repair twice. Same error.
I opened the SQL view,
SELECT DISTINCT DataTable.Q_230200
FROM DataTable;
I removed the DISTINCT, and it works. I went back to the original q
My query is fairly complex and in order to try your solution, I started removing tables I could live without. I wpuld remove a table and then test it. Still bad. Remove. Test. Bad. Until there was just the main table where the majority of the data lived. Then I got the error, "The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data." [OK] [Help] OK closes it, Helpbrings up a blank screen. This is a select query. I removed the remaining fields until there was one: the memo field. I still get the "field is too small" error. Compact and repair twice. Same error.
I opened the SQL view,
SELECT DISTINCT DataTable.Q_230200
FROM DataTable;
I removed the DISTINCT, and it works. I went back to the original q
ASKER
Computers are really strange.
My query is fairly complex and in order to try your solution, I started removing tables I could live without. I wpuld remove a table and then test it. Still bad. Remove. Test. Bad. Until there was just the main table where the majority of the data lived. Then I got the error, "The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data." [OK] [Help] OK closes it, Helpbrings up a blank screen. This is a select query. I removed the remaining fields until there was one: the memo field. I still get the "field is too small" error. Compact and repair twice. Same error.
I opened the SQL view,
SELECT DISTINCT DataTable.Q_230200
FROM DataTable;
I removed the DISTINCT, and it works. I went back to the original q
My query is fairly complex and in order to try your solution, I started removing tables I could live without. I wpuld remove a table and then test it. Still bad. Remove. Test. Bad. Until there was just the main table where the majority of the data lived. Then I got the error, "The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data." [OK] [Help] OK closes it, Helpbrings up a blank screen. This is a select query. I removed the remaining fields until there was one: the memo field. I still get the "field is too small" error. Compact and repair twice. Same error.
I opened the SQL view,
SELECT DISTINCT DataTable.Q_230200
FROM DataTable;
I removed the DISTINCT, and it works. I went back to the original q
ASKER
...continued...
I went back to the original query, removed the DISTINCT, and it works! There are duplicates, however.
I started with a clean query, put in
SELECT DataTable.Q_230200
FROM DataTable;
And it worked. I added the DISTINCT and it failed with the "field is too small" error.
I will work to get the duplicates out without using DISTINCT. Does anyone know why DISTINCT caused the fields to be shortened?
I went back to the original query, removed the DISTINCT, and it works! There are duplicates, however.
I started with a clean query, put in
SELECT DataTable.Q_230200
FROM DataTable;
And it worked. I added the DISTINCT and it failed with the "field is too small" error.
I will work to get the duplicates out without using DISTINCT. Does anyone know why DISTINCT caused the fields to be shortened?
DISTINCT does about the same thing as a GROUP BY clause including all selected fields. I know (I recently had this problem) that if you GROUP BY a Memo type field, it gets truncated to 255 characters - it makes sense that Access won't group by an arbitrary length field. DISTINCT is probably doing the same thing.
If your original query was DISTINCT, this may make the re-joining solution I gave unnecessary.
Try doing a "dummy" rpt then copy and paste the textbox into your real rpt
Works fine for me!
Good Luck!
Dave