Cesar --

Alan has responded to this in several message, so I won't go into the SQL issues.

You're finding the customers that have accounts, I assume.

Is the memo related to the customer? If so, then perhaps your data design would benefit from a customer table with a key into the accounts table. The customer table would maintain this memo information and would be able to report it with a join condition to your query on the account table.

I wouldn't assume that you'd be querying a memo related to the account, since your concern is customers, but perhaps that is the case.

Some thoughts...

Jay

>What would you do if you had a MEMO field as part of the non aggregate statement in VFP7. I can't return MAX of that. Nor can I add that to the GROUP BY statement. Is there any other way to make it aggregate?
>
>
>>>I am not sure I understand your suggestions, could you give me a sample line of code? Thanks for your time.
>>
>>3 options: Not all applicable in all situations.
>>
>>ORIGINAL
>>

>>SELECT name_line1, first_name, last_name FROM accounts ;
>>WHERE NOT EMPTY(last_name) ;
>>GROUP BY name_line1 ;
>>ORDER BY last_name INTO ARRAY aClientNames
>>

>>
>>ELIMINATE NON-GROUPED FIELDS FROM FIELD LIST
>>

>>SELECT name_line1 FROM accounts ;
>>WHERE NOT EMPTY(last_name) ;
>>GROUP BY name_line1 ;
>>ORDER BY last_name INTO ARRAY aClientNames
>>

>>
>>ADD AGGREGATE FUNCTIONS TO NON-GROUPED FIELDS
>>

>>SELECT name_line1, MAX (first_name), MAX (last_name) FROM accounts ;
>>WHERE NOT EMPTY(last_name) ;
>>GROUP BY name_line1 ;
>>ORDER BY last_name INTO ARRAY aClientNames
>>

>>
>>ADD NON-GROUPED FIELDS TO GROUP BY CLAUSE
>>

>>SELECT name_line1, first_name, last_name FROM accounts ;
>>WHERE NOT EMPTY(last_name) ;
>>GROUP BY name_line1, first_name, last_name  ;
>>ORDER BY last_name INTO ARRAY aClientNames
>>

>>
>>In your example, which, if I understand correctly, only 1 first and last name can possibly be returned with name_line1, this syntax would appear to be redundant. In most cases, it isn't.
>>
>> HTH,
>> Jay