If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Preventing query from converting memo field to text field.
I have a memo field that the user can insert markers that will be replaced
with data in a query process. Example: Dear {1} where the {1} will be replaced with a persons name in the query. The final results are placed in a different files memo field which is in turn used on a report. Although the entire memo field conversion resides in the second files memo field (looks good at this point) when that memo field is used on the final query that pulls all the data from several files to be used on a report, the memo field is cut at 255 characters like a text field although it was taken directly from a memo field where it was all there. Does anyone have an idea of the cause? Thanks |
#2
|
|||
|
|||
A memo field will be truncated to 255 characters if:
a) there is any formatting of the field, or b) Access performs any aggregation on the field. For a), check if there is anything in the Format property of the field in the table, or in the Format property of the text box on the report. For b), check that the source query does not have a DISTINCT predicate. If it has a GROUP BY clause, use First under the memo field instead of Group By, so that Access can just grab the whole of the first match instead of trying to group on the field. It's unusual to use a memo field for grouping in the Sorting'n'Grouping box of the report, but you could check there also. -- Allen Browne - Microsoft MVP. Perth, Western Australia. Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "Dennis In Forks" wrote in message ... I have a memo field that the user can insert markers that will be replaced with data in a query process. Example: Dear {1} where the {1} will be replaced with a persons name in the query. The final results are placed in a different files memo field which is in turn used on a report. Although the entire memo field conversion resides in the second files memo field (looks good at this point) when that memo field is used on the final query that pulls all the data from several files to be used on a report, the memo field is cut at 255 characters like a text field although it was taken directly from a memo field where it was all there. Does anyone have an idea of the cause? Thanks |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Condensing Text fields into a Memo field - Need to retain line spa | Doc Don Sturgiss | General Discussion | 3 | December 28th, 2004 02:43 AM |
Advanced query on numbers stored in a text field. | Dub333 | Running & Setting Up Queries | 8 | October 27th, 2004 12:16 PM |
Paramter Query with a memo field | Geof Wyght | Running & Setting Up Queries | 6 | October 25th, 2004 01:26 PM |
Memo Field data truncated in query | Joel | Running & Setting Up Queries | 3 | August 4th, 2004 03:40 PM |
Converting Field Names to Text | Dawn | General Discussion | 1 | May 16th, 2004 07:57 AM |