A Microsoft Office (Excel, Word) forum. OfficeFrustration

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.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Running & Setting Up Queries
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Truncation of memo fields in SELECT queries - Access 2002



 
 
Thread Tools Display Modes
  #1  
Old January 26th, 2005, 11:35 PM
datawizzard
external usenet poster
 
Posts: n/a
Default Truncation of memo fields in SELECT queries - Access 2002

After an extensive search of the MS knowledge base, I still can't find an
answer:

I have a simple SELECT query joining two tables, and I use the query as the
data source for a form. One of the tables contains memo fields that I want
to display on the form. I have the "Unique Values" property set to "Yes" to
avoid getting duplicate results. When I run the query, the memo fields are
truncated at 255 characters. This only happens when the "Unique Values"
property is set to "Yes". I know that Access will only use the first 255
characters of a Memo field to do comparisons for a Parameter query, and the
"Unique Values = Yes" setting does cause internal comparisons to take place
when Access runs my SELECT query, even though it's not a Paramater query.
However, I've found nothing that says memo fields will be truncated in the
result set in any scenario! Is there a way around this? Or is it an
"undocumented feature" of MS Jet . . .

(Using MS Jet version 4.0.6218.0)
  #2  
Old January 27th, 2005, 12:46 AM
John Vinson
external usenet poster
 
Posts: n/a
Default

On Wed, 26 Jan 2005 14:35:02 -0800, "datawizzard"
wrote:

I have the "Unique Values" property set to "Yes" to
avoid getting duplicate results. When I run the query, the memo fields are
truncated at 255 characters.


Yep. This is well known behavior.

It's not really a "bug" though you're quite right that it should be
better documented. After all, a Memo field could contain a gigabyte of
data - having Access compelled to check the gigabyte of data in this
record with the gigabyte of data in the next record to discover that
they are different in the 942,845,298th byte is perhaps a bit
unreasonable! g

What you can do to exclude duplicates on the *remaining* fields is to
use a Totals query; Group By the fields other than the memo (and, if
you wish, on a calculated field Left([memofield], 255); and use the
First operator on the memo field to find the first instance of the
memo field in the group. If your data contains records where the ONLY
difference between the records is past the 255th byte in the memo
field you'll miss that fact (and see only the first of the
near-duplicates). If your data has such records I don't know of a good
way to de-duplicate them though!

John W. Vinson[MVP]
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Top 20 and bottom 20 values Brian Camire Running & Setting Up Queries 9 January 8th, 2005 02:36 AM
BUG: Using GROUP BY in query expression on MEMO fields it truncates data in MEMO fields to first 255 characters [SolarAngel] General Discussion 5 December 7th, 2004 07:29 PM
BUG: Using GROUP BY in query expression on MEMO fields it truncates data in MEMO fields to first 255 characters [SolarAngel] Running & Setting Up Queries 5 December 7th, 2004 07:29 PM
memo field truncation: new problem whincup Running & Setting Up Queries 2 November 16th, 2004 09:40 AM
Word 2000/2002 - Proper Mail Merge steps for ODBC? Tony_VBACoder Mailmerge 7 September 2nd, 2004 09:21 PM


All times are GMT +1. The time now is 08:20 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.