255chr txt field limit on reports?

[jmash]

I cant seem to get beyond 255 characters, even though the field in the table it pulls from and the form shows it has way more text in it. Help says to use an OLE object and thats all, so I've tried inserting a word pad, or word object in the report, but then I cant get any data into it from the the queried field that has more than 255 characters from the orginal table field.

Any advice or workaround on this? I've been wracking my brain on this for months and having to manually cut and paste text from the form into an email I generate from the report.

Thanks very much if know!

 

[WayneRyan]

jmash,

The report can display memo fields way longer than 255 characters.

Check the query that is feeding your report. I'll bet that that's where
the truncation occurs. I'm not sure exactly, but certain joins and things
like UNIONs will cause data truncation.

hth,
Wayne

 

[jmash]

After checking it does seem to be truncating the text from the table's memo field in the query stage, but I still can't figgure out where exactly.

I did find this in Access Help It says:


You can sort or group on a Text field or a Memo field, but Access only uses the first 255 characters when you sort or group on a Memo field.


I don't think I'm grouping on that field, but it does have all fields set to Group By includeing this for totals which I can't seem to get the query to run if I change that to something else like sum or val or expression. Theres a bunch of difrent totals to try, maybe one will work eventually. Not even sure if that has anything to do with it.

I'm still trying, anymore ideas please post me again. Thanks!

 

[jmash]

Turns out it was the Group By Total calculation in the query. Why it was there in the first place I don't quite understand, but it makes sense to limit the field size on a calculation. I didn't need that anyway since it was a memo field and remade the query without any Group Bys. No more limit yeah!

I had to do some sniffing out, but at least you helped me in the right direction that it was in the query not the report.

Thanks!