Hi Dan,
Thank for your reply.
Yes, as you see, memo field will be truncate if you leave Group By under
memo field.
The KB as below descript this issue. Hope this helpful to you.
http://support.microsoft.com/kb/250640/en-us
[PRB: GetChunk Ignores Offset if Memo Field Is Included in GROUP BY]
The workaround is to rewrite the query to eliminate all Memo fields from
the GROUP BY clause. This can be done by using an aggregate function on the
Memo fields, such as the FIRST function. This allows the Memo fields to be
removed from the GROUP BY clause.
To your special case, the query command could be changed as
SELECT Stories.StoryTitle, Stories.Synopsis, First (Stories.Story)
COUNT(Comments.CommentID) AS ComCount
FROM (Stories LEFT OUTER JOIN Comments ON Stories.StoryID =
Comments.StoryID)
WHERE (Stories.StoryID = ?)
GROUP BY Stories.StoryTitle, Stories.Synopsis
Additionally, this doesn't mean we could only use one memo field in a query
which uses a GROUP BY clause. If you have more than one memo field, you can
use First under all this memo field.
For example:
Select c1, First (c2), First (c3) from table group by c1.
Both c2 and c3 are memo filed.
Please don't hesitate to let me know if you have any further question.
Have a great day.
Best regards,
Wen Yuan