Memo fields being truncated

[Timtropolis]

Hi all,

I've seen this topic posted but haven't seen any answers that fit or work so I'll post again.

I am desiging a database in Access2002. The database has approximately 15 memo fields across 5 tables. My issue is that when I write my query to pull in the memo fields for a report, the memo fields are being truncated, but not all the time. I have 3 fields, a Control and Issues field which are being truncated at 255 characters and an Action plan field which doesn't get truncated at all.

Inspection of the data in the tables shows no truncation so I know my import functions are working correctly. The query is where I see the truncation. Here are some particulars:

> I am not using any aggregate functions in the query (I understand that
aggregate queries or queries using calculations/totals will cause problems).
> I do create some custom fields on the fly that I use for sorting purposes
(since you can't sort on a memo field).
> the amount of the data in memo fields are not overly huge... nothing over
3000 characters

At this point I'm stumped and would appreciate any input on anyone who has knowledge of this problem.

TIA,
Tim

 

[The_Doc_Man]

the amount of the data in memo fields are not overly huge... nothing over 3000 characters

I have 3 fields, a Control and Issues field which are being truncated at 255 characters and an Action plan field which doesn't get truncated at all.

The limit on TEXT fields is also 255 characters, which makes me think that somehow Access is confused about the field it is viewing. Is there any chance that a TEXT (not MEMO) field is involved here such that there is confusion about the Control and Issues fields?

Does the order of appearance of the fields in the query make a difference?

Jenna has also posted this problem in this same forum. You two should talk to each other. Or watch her post of today. Sounds like you might have the same problem.

 

[Timtropolis]

A solution???

Thanks for responding Doc, and no, the fields have been properly defined. That was my first check. From what I can tell, order does not make a difference but what did make a difference was this:

when I broke the query down at rebuilt it from scratch (checking each time I added a table to see if there was any truncation) it worked!! Don't ask me how or why cause I honestly don't know. I used the same joins and the same fields in the same order along with the same criteria. Gotta love Access