[AccessD] More in Queries and Memo Fields

At first blush my thought was like Dan's... If the whole point of NOT
truncating the field is because you want to two records which have different
comments to appear as separate records - then taking First() doesn't seem to
get you further ahead.

But it is VERY GOOD to be warned that I will never get what I need from a
MEMO field, and that I am fooling myself in using it in a Group By.

BTW ... the memo field was changed to text a long, long time ago

;-)



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Tuesday, July 12, 2011 3:34 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] More in Queries and Memo Fields

>From Allen Browne’s site: (http://allenbrowne.com/QueryPerfIssue.html)

-------------------
This makes a major difference with Memo fields. If you GROUP BY a memo
(Notes in the example), Access compares only the first 255 characters, and
the rest are truncated! By choosing First instead of Group By, JET is free
to return the entire memo field from the first match. So not only is it more
efficient; it actually solves the the problem of memo fields being chopped
off.

(A downside of using First is that the fields are aliased,
e.g. FirstOfNotes.)
-------------------

Dan



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com